Earlier quoted context omitted.
Flutter founder here. When I led the Google team we had pretty good analytics. `flutter` was for a long time opt-out with analytics and would phone home to Google and report usage. We filtered out docker containers and things that looked like CI and saw usage near 1M monthly actives when I left Google a couple years ago. I'm sure it's up since then. There are 10s of millions of web developers in the world. Doesn't sh…
Are there any statistics on how much of it is used in production?
We're forking Flutter
41–50 of 748 posts
Re: We're forking Flutter
#42They estimate there are one million Flutter developers/users. Have I been sleeping under a rock?
It's possible that they also count students and amateurs such as me, who only used it in a small project never published. There could be a million I guess, but professional developers are probably a lot less.
Re: We're forking Flutter
#43I only see a single name?
Is this just some dude with a blog?
Re: We're forking Flutter
#44Earlier quoted context omitted.
Flutter founder here. When I led the Google team we had pretty good analytics. `flutter` was for a long time opt-out with analytics and would phone home to Google and report usage. We filtered out docker containers and things that looked like CI and saw usage near 1M monthly actives when I left Google a couple years ago. I'm sure it's up since then. There are 10s of millions of web developers in the world. Doesn't sh…
Are there any statistics on how much of it is used in production?
Re: We're forking Flutter
#45Earlier quoted context omitted.
Are there any statistics on how much of it is used in production?
If there would be 1M flutter devs per year and on average team had 10 devs (rather rare most mobile teams would be smaller except really big apps) and development of app would take ~1 year you would expect minimum 100k new flutter apps in app store every year. That seems highly unlikely.
Re: We're forking Flutter
#46The SQLite developers must find this rationale hilarious.
Re: We're forking Flutter
#47> That's 50 people serving the needs of 1,000,000. Doing a little bit of division, that means that every single member of the Flutter team is responsible for the needs of 20,000 Flutter developers! That ratio is clearly unworkable for any semblance of customer support. Back when I worked on .net we had fewer than 50 people maintaining a product that shipped to over a billion machines. If you opened an issue on github…
The constant pressure to ship new features instead of only widely desired features overtaxes a team quickly.
Re: We're forking Flutter
#48Earlier quoted context omitted.
> There have been similar projects based on technologies that Microsoft has killed Isn't flutter from google?
Yes, it is. I was just thinking about what happened when other companies did something similar.
Re: We're forking Flutter
#49Key statement: "As Flock ships important bug fixes and features, the Flutter team can then choose to add those to Flutter, on their schedule. " I see a lot of negative comments but I think this will be a net positive over time to the Flutter community and to the technology itself. I think it will also give Google a reality check on the needs of the community.
Re: We're forking Flutter
#50> That's 50 people serving the needs of 1,000,000. Doing a little bit of division, that means that every single member of the Flutter team is responsible for the needs of 20,000 Flutter developers! That ratio is clearly unworkable for any semblance of customer support. Back when I worked on .net we had fewer than 50 people maintaining a product that shipped to over a billion machines. If you opened an issue on github…