6 ms·
I know a construction worker, a recruiter and a mechanical Engineer, among other random professions, that moved to JS without much trouble. It somehow seems ove
by franciscop 4y ago
I know a construction worker, a recruiter and a mechanical Engineer, among other random professions, that moved to JS without much trouble. It somehow seems overwhelmingly that it's other fellow devs that have trouble with getting started JS.
TBF right now JS is in transition from commonjs to ESM, and we all believe for the better, but this transition period does yield some strange issues like the article said, for instance I hope/expect that "Warning: To load an ES module [...]" will be default in the near future so we won't need that warning anymore.
Also knowing JS enough, if I see "SyntaxError: Cannot use import statement outside a module" coming from a package I'd know that the package is wrong, at which point I would just try to find other of the 2M+ packages, open the JS file to see how it works if I'm really interested, open an issue or assume the project is just broken (which just happens, not all packages are well built).
- emn13 4y agoThe difference likely is that they didn't do what these people did - try to use some package from scratch. It's much easier to take a sample and extend it, especially if you can join a team and hop onto their running, fully-fledged project. The JS tooling story _is_ convoluted, and most people just don't touch that stuff, or when they do, they start from a working place, and just make small tweaks.
- thegeomaster 4y agoBut the problem is, JS has been in a transition from some X to some Y for the last 10 years.
- corrral 4y agoA little longer than that. Everything went to shit basically as soon as Node hit the scene—not sure if it can be blamed for it, exactly, but the timeline fits.
- franciscop 4y agocommonjs to ESM is the first truly breaking change that the JS ecosystem has experienced, everything else was a lot smoother