News for hackers. Stuff that matters.
Re:Dear Google Cloud: Your Deprecation Policy Is Killing You by jimmaswell on Saturday August 15, 2020 @03:11AM (#24166714)
The absolute worst in my small experience with it is anything touching the node ecosystem. Try to follow any guide or use any library not updated in the last week and there will be breaking API changes and deprecation warnings everywhere.
Re:Dear Google Cloud: Your Deprecation Policy Is Killing You by BossingAround on Saturday August 15, 2020 @06:02AM (#24167607)
I'm running into this problem more and more. It seems like Node is fundamentally unusable for anything but the nimblest teams that do not mind updating their dependencies automatically, every week, and when something breaks, they are capable of fixing it within hours.

I really like Node as a language (especially with TS), but Node as an ecosystem feels like a very hard fit into 90%+ of corporations.

Re:Dear Google Cloud: Your Deprecation Policy Is Killing You by nicoburns on Saturday August 15, 2020 @06:23AM (#24167746)
I think the culture of Node comes from the earlier culture of in-browser JavaScript. When running on the browser platform you have to make sure your libraries are up to date and maintained, otherwise you're at the mercy of browser updates breaking things from under your feet (this is less bad now, but it was awful in the days of IE<9, and on android before they started shipping auto-updating Chrome webview)

Consequently, JavaScript developers got used to the burden of maintenance and rapidly updating to the latest versions of libraries, and this culture carried through to Node (partly because a lot of libraries are shared between node and the web).

Having said that, if you pick your libraries well, it's not too bad these days. When I upgraded from Node 12 to Node 14 earlier this year, I had to upgrade the `pg` package to a newer version that supported Node 14 (there was one available), but I didn't have to make any code changes. And other than that I've had no forced version upgrades in a long time.

I guess if you're lookig at 5-10 year timescales with literaly no maintenance then this would be a different matter though.

Re:Dear Google Cloud: Your Deprecation Policy Is Killing You by dutchmartin on Saturday August 15, 2020 @07:11AM (#24168018)
I strongly feel that you must have end to end tests while using node because of the dependency hell. Not even knowing if a upgrade of a dependency breaks your system is just hard. Also testing it by hand is just not maintainable.
Re:Dear Google Cloud: Your Deprecation Policy Is Killing You by joepie91_ on Saturday August 15, 2020 @08:06AM (#24168286)
> Not even knowing if a upgrade of a dependency breaks your system is just hard.

This is true for any language/platform.

Re:Dear Google Cloud: Your Deprecation Policy Is Killing You by john-shaffer on Saturday August 15, 2020 @01:07PM (#24170380)
There are massive differences in how much of a problem this is across different platforms.

With Clojure, I can think of 2 times ever when a dependency caused an issue. It was extremely obvious since the issue was "won't compile", and the fixes were simple.

With PHP, I expect any change to potentially break something. Bump your AWS SDK which uses a different minor version of guzzle? Fatal error.

There's a world of difference between breakage being an everyday thing and a true rarity.

Re:Dear Google Cloud: Your Deprecation Policy Is Killing You by nl on Saturday August 15, 2020 @08:18AM (#24168339)
Strong typing does partially help in this situation though.
Re:Dear Google Cloud: Your Deprecation Policy Is Killing You by tsimionescu on Saturday August 15, 2020 @08:56AM (#24168522)
Only for the most trivial bugs, though (as non-dependent type systems can't express anything but trivial properties). Still, it's better than nothing.
Re:Dear Google Cloud: Your Deprecation Policy Is Killing You by joepie91_ on Saturday August 15, 2020 @08:05AM (#24168279)
This is only a problem in some parts of the ecosystem - but they are the parts that most 'tutorials' are written about, because they look shiny and fancy. If I'm blunt, they're the parts of the ecosystem that HN loves to gloat about in their "how I saved my company thousands of dollars by building a todo app with GlamorousLibraryJS" type posts.

The short answer: if you avoid the shiny tools that claim to do everything, you will not have this problem. And as a special case, avoid Gulp, which is mismanaged.

The single-responsibility libraries that have a well-defined scope, on the other hand, have often been sitting on npm unchanged for 5-6 years, because they are simply done, and they do what they need to. They will very likely never deprecate anything, as there is simply nothing to change.

I would argue that these libraries are actually doing a better job of stability than their counterparts in other languages.

Edit: An additional factor is that it's easy to write a tutorial about an extensive framework with a large scope; there's plenty of stuff to write about. Writing a tutorial about "this is how you make a function call to this library to parse a geo URI", on the other hand, probably isn't going to happen.

So if you follow third-party tutorials, you are naturally going to end up at the packages that are most prone to deprecations.

Re:Dear Google Cloud: Your Deprecation Policy Is Killing You by kungato on Saturday August 15, 2020 @04:41AM (#24167150)
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
Re:Dear Google Cloud: Your Deprecation Policy Is Killing You by joepie91_ on Saturday August 15, 2020 @08:08AM (#24168293)
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

Re:Dear Google Cloud: Your Deprecation Policy Is Killing You by RonanTheGrey on Saturday August 15, 2020 @03:23PM (#24171527)
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.

Re:Dear Google Cloud: Your Deprecation Policy Is Killing You by nl on Saturday August 15, 2020 @08:19AM (#24168344)
Tensorflow is another example of this.
Re:Dear Google Cloud: Your Deprecation Policy Is Killing You by sukilot on Sunday August 16, 2020 @11:39AM (#24178627)
Google was better when they were smaller. Java Guava rules.
Re:Dear Google Cloud: Your Deprecation Policy Is Killing You by nicoburns on Saturday August 15, 2020 @06:25AM (#24167758)
Google aren't very good at this, but Facebook are. Maybe give React a try.
Re:Dear Google Cloud: Your Deprecation Policy Is Killing You by LoSboccacc on Saturday August 15, 2020 @03:24AM (#24166777)
try using four libraries and chances are they require two different version of a build tool installed globally
Re:Dear Google Cloud: Your Deprecation Policy Is Killing You by userbinator on Saturday August 15, 2020 @08:29PM (#24173702)
Anything Node, JS, or web-development related seems to churn much more than everything else.