5 ms·
I’d agree with you except for the fact that it’s really hard to say that developer experience today is better than what it was before. Especially once you adjus
by addicted 5y ago
I’d agree with you except for the fact that it’s really hard to say that developer experience today is better than what it was before. Especially once you adjust for the fact that browsers are so much better and standardized.
- krapp 5y agoDownloading and installing JQuery and some plugins versus the Byzantine nightmare of dependencies, transpilation and hacks upon hacks that is modern JS development? It was objectively better in every respect before.
- jakelazaroff 5y agoUntil your dependencies start to form a tree, and you can't just rely on all the global variables being loaded in the right order anymore… Vendoring every dependency and having to manually keep track of all the updates was objectively worse than NPM as well.
- krapp 5y agoThen again, having a couple of .js files just sitting on my server meant some rando having a temper tantrum and deleting their repo wouldn't break my site, or half of the internet.
- jakelazaroff 5y agoThat also won’t happen with NPM.
- krapp 5y agoOnly because it happened once and then they fixed it, but it was never a problem in the old days. Having one company and one package manager act as a single point of failure for essentially all of the javascript in the universe was a bad idea. It looks and feels a lot more like "real" programming now but the whole house of cards seems to tip over and burst into flames every other week.
- jakelazaroff 5y agoI think this is a bit hyperbolic for a problem that happened once and then they fixed it. I also don't really know what you're talking about with regard to the house of cards constantly tipping over…? It honestly just seems like you have an axe to grind here.
- deleted 5y ago[deleted]