> We describe Flock as "Flutter+". In other words, we do not want, or intend, to fork the Flutter community. Flock will remain constantly up to date with Flutter. That was the first fear when I saw the title - splitting community and having two incompatible versions. Good to see it addressed in the post. The second was just a fear of how it would complicate the development process, but it seems to be a drop-in replac…
We're forking Flutter
231–240 of 748 posts
Re: We're forking Flutter
#232Earlier quoted context omitted.
I’m not sure what you mean by this but Python can be very performant when you want it to be. That is to say, when you build computation heavy parts in C (or Zig), and remember to avoid the various performance pitfalls like not using generators when you didn’t want to load all those millions of elements into your memory. What sets professional Python aside from most other programming languages is that everyone who use…
So, basically: Python is performant when you don't use Python?
Re: We're forking Flutter
#233> We describe Flock as "Flutter+". In other words, we do not want, or intend, to fork the Flutter community. Flock will remain constantly up to date with Flutter. That was the first fear when I saw the title - splitting community and having two incompatible versions. Good to see it addressed in the post. The second was just a fear of how it would complicate the development process, but it seems to be a drop-in replac…
> Most people don't realize how many apps written in Flutter they use daily, simply because it's impossible to tell You can't be serious. Maybe on Android, but on other platforms—especially iOS—they stick out like a sore thumb. A number of them just look like Material Design Android apps awkwardly transplanted over, but I know that's down to the developer so I won't hold that against Flutter. But scrolling through th…
Re: We're forking Flutter
#234Earlier quoted context omitted.
50 people is a pretty huge team at Google to start with, there’s teams of <5 that support weird bits of core infrastructure that serve billions of users an hour.
Exaggeration? Billions per HOUR seems quite a stretch there..
Re: We're forking Flutter
#235Earlier quoted context omitted.
> Flutter Founder here. Flutter was a company acquired ala Firebase? Always thought it was a project (like Golang) incubated by/for/at Google.
No Eric founded Flutter at Google. However, Google had previously acquired another company called Flutter, and they had that domain lying around, and decided to use it. That's what I understood, at least.
Re: We're forking Flutter
#236I'm confused .. is this a Google-led fork? Is "Flutter Foundation" a google sponsored foundation? If not, why use "Flutter" trademark? Also, if the fork is called "Flock", why is this called a "Flutter Foundation"?
Google is the „owner“ of flutter, why would they fork their own thing? The post is describing the problem the author has with google.
Re: We're forking Flutter
#237> We describe Flock as "Flutter+". In other words, we do not want, or intend, to fork the Flutter community. Flock will remain constantly up to date with Flutter. That was the first fear when I saw the title - splitting community and having two incompatible versions. Good to see it addressed in the post. The second was just a fear of how it would complicate the development process, but it seems to be a drop-in replac…
Which flutter apps do I likely use?
Re: We're forking Flutter
#238Earlier quoted context omitted.
> Flutter Founder here. Flutter was a company acquired ala Firebase? Always thought it was a project (like Golang) incubated by/for/at Google.
No Eric founded Flutter at Google. However, Google had previously acquired another company called Flutter, and they had that domain lying around, and decided to use it. That's what I understood, at least.
Re: We're forking Flutter
#239> We describe Flock as "Flutter+". In other words, we do not want, or intend, to fork the Flutter community. Flock will remain constantly up to date with Flutter. That was the first fear when I saw the title - splitting community and having two incompatible versions. Good to see it addressed in the post. The second was just a fear of how it would complicate the development process, but it seems to be a drop-in replac…
> Most people don't realize how many apps written in Flutter they use daily, simply because it's impossible to tell You can't be serious. Maybe on Android, but on other platforms—especially iOS—they stick out like a sore thumb. A number of them just look like Material Design Android apps awkwardly transplanted over, but I know that's down to the developer so I won't hold that against Flutter. But scrolling through th…
Re: We're forking Flutter
#240Earlier quoted context omitted.
> Most people don't realize how many apps written in Flutter they use daily, simply because it's impossible to tell You can't be serious. Maybe on Android, but on other platforms—especially iOS—they stick out like a sore thumb. A number of them just look like Material Design Android apps awkwardly transplanted over, but I know that's down to the developer so I won't hold that against Flutter. But scrolling through th…
Sure, but not every cross-platform app developer wants their app to look "native to iOS". Especially if you want your app to look the same on all platforms and/or have some creative design.