The big question is who will pay for maintaining the Flock. It's all great for the first half year when folks have some cash lying around, but then the reality check comes, and they need money to survive. The most important effort with Flock should be raising money so that everyone is sure that the project won't die.
Importantly, the Dart and Flutter teams are totally distinct, and the rate the dart team closes bugs has no relation at all to the Flutter team. Matt is specifically speaking to Flutter issues.
I love Viktor’s expression of panic when bugs were discussed 😂 Dude’s mind is certainly racing and thinking „am I getting in trouble with Google overlords and potentially hurting my very google-dependent company?”
I don't think this is anything new; it seems to be a pattern for Google to launch products only to later retire them. If they truly believe they're not heading in that direction with Flutter, the most professional approach would be to publish a clear roadmap for the next five to ten years. This would help developers and organizations feel confident in adopting Flutter, knowing it has a stable, long-term future. We're not here to point fingers-it’s reasonable for any company to focus on products that generate revenue. But Flutter is different from past projects that ended up in the "Google graveyard." A well-defined roadmap would reassure developers and encourage broader adoption.
Given the uncertainty about how AI is going to affect software development it's not clear what the most important priorities are in two/three years the way you would need for a five year roadmap. On the other hand a roadmap wouldn't prevent Google from reducing their spending in Flutter in the future, so the amount of developer reassurance wouldn't be that great.
Regarding the foundation thing mentioned at 00:16:00, we had a community discussion at the Flutter & Friends conference, there are definitely some updates there. Matt, you should definitely reach out to Simon if you or he haven't done that already.
While nothing is certain, Flutter's current trajectory suggests Google's continued support. Worst-case scenario: If Google were to "kill" Flutter, the community would likely: 1. Fork the project. >> Flutter isn't going to die...... it will live just like linux, so flock is right........and we must add to that.. 2. Continue development. 3. Ensure compatibility. Flutter's open-source nature guarantees its survival.
![Stromae, Pomme - “Ma Meilleure Ennemie” (from Arcane Season 2) [Official Visualizer]](http://i.ytimg.com/vi/1F3OGIFnW1k/mqdefault.jpg)
The big question is who will pay for maintaining the Flock. It's all great for the first half year when folks have some cash lying around, but then the reality check comes, and they need money to survive. The most important effort with Flock should be raising money so that everyone is sure that the project won't die.
Importantly, the Dart and Flutter teams are totally distinct, and the rate the dart team closes bugs has no relation at all to the Flutter team. Matt is specifically speaking to Flutter issues.
I love Viktor’s expression of panic when bugs were discussed 😂 Dude’s mind is certainly racing and thinking „am I getting in trouble with Google overlords and potentially hurting my very google-dependent company?”
I can't wait what will happen!
I do agree with Matt does problems are real
I don't think this is anything new; it seems to be a pattern for Google to launch products only to later retire them. If they truly believe they're not heading in that direction with Flutter, the most professional approach would be to publish a clear roadmap for the next five to ten years. This would help developers and organizations feel confident in adopting Flutter, knowing it has a stable, long-term future. We're not here to point fingers-it’s reasonable for any company to focus on products that generate revenue. But Flutter is different from past projects that ended up in the "Google graveyard." A well-defined roadmap would reassure developers and encourage broader adoption.
Given the uncertainty about how AI is going to affect software development it's not clear what the most important priorities are in two/three years the way you would need for a five year roadmap. On the other hand a roadmap wouldn't prevent Google from reducing their spending in Flutter in the future, so the amount of developer reassurance wouldn't be that great.
Lets maintain the flutter like the linux which is also open source
Regarding the foundation thing mentioned at 00:16:00, we had a community discussion at the Flutter & Friends conference, there are definitely some updates there. Matt, you should definitely reach out to Simon if you or he haven't done that already.
While nothing is certain, Flutter's current trajectory suggests Google's continued support.
Worst-case scenario:
If Google were to "kill" Flutter, the community would likely:
1. Fork the project. >> Flutter isn't going to die...... it will live just like linux, so flock is right........and we must add to that..
2. Continue development.
3. Ensure compatibility.
Flutter's open-source nature guarantees its survival.
Does Matt have his own RUclips channel?
I'll file with Flock and wish you could change the name to Flutter++ if it doesn't a trade mark issue
Is this going to be expo version of flutter?
Lets make team big, so many it in india use flutter even startup prefer flutter
🎉🎉🎉