Hacker News new | past | comments | ask | show | jobs | submit login

> Meanwhile in JS it seems like you can’t go more than six months without having to rewrite something.

And by "in JS", you really mean, "in NPM land".

So long as folks keep remaining seemingly (almost willfully) ignorant of the source of their pain and/or running right back into the fire the next time the opportunity presents itself, that pain is going to continue.

NPM sucks. It's not the way to do JS. Everyone who has ever experienced it and then written a complaint about it should be more than willing to accept this. For whatever reason, though, they aren't. (My hypothesis? They like being able to write about their pain because it gives them something and someone to kvetch about/to. See Aurornis above/below on the role of social media and influence in "FE" (i.e. browser-focused software development), and Alex Danco's "Making is Show Business Now" <https://alexdanco.com/2020/10/08/making-is-show-business-now...>.)




the problem is that as with everything else in FE it is kind of hard to tell what successor framework will "win" and not do this to you.

Svelte and Vue were nice and stable until they were not, Deno as an alternative to NPM kind of never got any traction, and unfortunately no one has come up with a better sandbox that works the same everywhere other than the web.


I understand why they had to EOL Vue 2 and make Vue 3 - I'm still facing migrating a couple of projects at some point, and I will keep putting it away x)

But is upgrading Vue 3 across minor versions that much of a pain? Actually curious about people's real world experience.


Also by “npm land” you mean “react-webpack-based bloated build- and eco-systems”.

NPM sucks. It's not the way to do JS

${X}PM is absolutely the way to do $X. You can’t survive without the PM part. You just have to know cancer when you see it and call it out rather than praising.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: