4 ms·

The sad part about the js ecosystem is that even the biggest corps like Google can't keep their own js ecosystem stable on the last version. I have a small Angu

The sad part about the js ecosystem is that even the biggest corps like Google can't keep their own js ecosystem stable on the last version. I have a small Angular app with Firebase backend and every time I come back to it to update, the libs are out of sync

nicoburns 6y ago
Google aren't very good at this, but Facebook are. Maybe give React a try.
joepie91_ 6y ago
Google is notoriously bad at maintaining (or even designing) their open-source stuff. I wouldn't say "even the biggest corps like Google" -- Google does considerably worse at this than many hobbyist maintainers! I just don't use Google libraries anymore, if I can at all avoid it. See also my other comment[1] - Angular is an example of such a magical does-everything framework. [1] https://news.ycombinator.com/item?id=24168279 https://news.ycombinator.com/item?id=24168279
- nl 6y ago
  Tensorflow is another example of this.
- RonanTheGrey 6y ago
  We've abandoned an app because of the inability to keep Firebase working on it (JS libraries). Between out of sync Typescript definitions, broken APIs, broken interfaces, "this version of some other dependency works with this version of Firebase thanks to some random transient dependency", it just became too much. We won't use the JS libraries at all anymore. Angular is the only one that has remained even remotely usable, but certainly not stable. It's never as simple as running the upgrade utilities, changing the version, and being done. It ALWAYS takes at least a day to find all the "little" things they didn't feel fit to mention in the upgrade docs. It's aggravating. I genuinely don't like using Google software, at all. I've felt for a long time that Google is coasting on the momentum of the early web and the awe people felt for what they built early on. That hasn't been Google for a long, long time.
- sukilot 6y ago
  Google was better when they were smaller. Java Guava rules.

nicoburns 6y ago

Google aren't very good at this, but Facebook are. Maybe give React a try.

joepie91_ 6y ago

Google is notoriously bad at maintaining (or even designing) their open-source stuff. I wouldn't say "even the biggest corps like Google" -- Google does considerably worse at this than many hobbyist maintainers! I just don't use Google libraries anymore, if I can at all avoid it. See also my other comment[1] - Angular is an example of such a magical does-everything framework. [1] https://news.ycombinator.com/item?id=24168279 https://news.ycombinator.com/item?id=24168279

nl 6y ago
Tensorflow is another example of this.
RonanTheGrey 6y ago
We've abandoned an app because of the inability to keep Firebase working on it (JS libraries). Between out of sync Typescript definitions, broken APIs, broken interfaces, "this version of some other dependency works with this version of Firebase thanks to some random transient dependency", it just became too much. We won't use the JS libraries at all anymore. Angular is the only one that has remained even remotely usable, but certainly not stable. It's never as simple as running the upgrade utilities, changing the version, and being done. It ALWAYS takes at least a day to find all the "little" things they didn't feel fit to mention in the upgrade docs. It's aggravating. I genuinely don't like using Google software, at all. I've felt for a long time that Google is coasting on the momentum of the early web and the awe people felt for what they built early on. That hasn't been Google for a long, long time.
sukilot 6y ago
Google was better when they were smaller. Java Guava rules.