Hacker News new | ask | show | jobs
by nickphx 1317 days ago
Why give up after all that effort?
2 comments

> “Why give up after all that effort?”

Because the speed of iteration in JS-framework-land is so fast that if you take more than a week or two setting up your dev environment your dependencies are already out of date and insecure, and the half of them that are using “require” instead of “import” stopped working with another library you depend on. Then, when you reported that, the maintainer replied to the GH issue, “modern browsers and Node releases have supported ESM loading for _ages_, like months and months before I started being a dev in 2018 so trust me, it’s stable now.”

(Not that I’ve had an experience like this, ever. And if so, not in a least six months. Or two. Whatever; I’m just slow, obviously.)

> Then, when you reported that, the maintainer replied to the GH issue, “modern browsers and Node releases have supported ESM loading for _ages_, like months and months before I started being a dev in 2018 so trust me, it’s stable now.”

Try this line with D3 :-) The maintainer, Mike Bostock, has been a developer since before Node and its commonjs modules. He dropped support of commonjs since d3 version 7, about a year and a half ago.

I remember the time I worked on a project with React Native and they broke a bunch of very useful tools by depending on an alpha of React in a release of RN. Stayed screwed up for a good long while. There were some issues posted on GH that were understandably like "bro, WT actual F?" and the maintainers were all "LOL we're with Facebook, trust us, it's fine".

And that was the day I decided RN was kinda bad.

Sounds like you’re a fan of the sunk cost fallacy.