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.
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