![[ Lu 1998 ]](https://media2.dev.to/dynamic/image/width=50,height=50,fit=cover,gravity=auto,format=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F731602%2F1b9d629c-1ae3-478b-a04a-95828af3d0ab.jpeg){kind=small}
First of all, Flutter is very good when it works, but it breaks so fast.
Whenever Team Flutter at google decides that oh whichever common feature is no longer supported, it makes every other GitHub repo nearly impossible to get to work. (FlatButton) for example, breaking every widget into a slew of errors, due to THE default button not being supported anymore (as of 3.0.~)
Getting an external flutter project to run from version to version, accommodating to pub package's compatibilities is a nightmare. Not even your own repos are safe from being deprecated into oblivion with the current embedding 2.0 changes.
It's kind of sad that one of the best frameworks for cross-platform development routinely turns everything built on it obsolete. So as to signal you to never use it for anything past of an experiment.
Like at what point are you sure to build a project upon a foundation that might not even exist in the very VERY near future.
Top comments (5)
I don't agree with this idea, it's not google's nor flutter's fault that we choose to use packages that are not well maintained or someones experiment or exercise. It's up to us to check whether the package is safe to use or not, "is it well maintain?", "when was the last time it was updated?", "do many people use it?", etc...
I spend quite a bit of time researching each package before jumping on board and using it in an app.
They also don't force you to update, it's usually safer to wait a while before updating to the newest version, this way we give package developers time to fix or update their packages.
PD: this is a problem with most frameworks (at least the ones I've tried), it's not flutter specific.
I've personally never had this level of trouble with JavaScript or java. Even using all the weird packages and whatnot
Fair enough. What exactly gave you problems? I might've been lucky and not encountered these problems
The wider community would disagree. In poll after poll each year, the Flutter community votes for breaking changes. Most of the community views breaking changes as a worthwhile tradeoff for improvement.
Of course, you can feel differently and some people do!