C J SilverioThis blog post is interesting in a number of ways.
Background: Flutter is a very popular toolkit for writing phone apps; it's probably the biggest? only? use case for Dart in the wild but it's a big use case.
Google has decided to pare down its support for Flutter, probably because they can't figure out a way to paste advertising all over it or something. The Google Flutter team is now years behind in dealing with bugs.
They say they welcome external contributors, but in practice they do not. From the article: "Everything takes forever, and it always seems to be about non-critical details.”
So the fix is to fork the project, take changes from upstream at whatever slow pace they arrive, and let the community do bugfixing and feature work at its own, much-faster pace.
A case of "yeah, gimme that, you're messing up” where the community takes an open source project away from a gigantic corporation rather than the reverse.
Nolan Lawson (@[email protected])
"We're forking Flutter. This is why." by Matt Carroll https://flutterfoundation.dev/blog/posts/we-are-forking-flutter-this-is-why/ This is fascinating. I'll be interested to see if this turns out like Node->io.js (projects eventually merge), Hudson->Jenkins (everyone moves to the fork), or something else.
Sab 