6 ms·
Progress, the one thing JS has too much of, too quickly, without stabilizing for quality. There are a number of benefits (see the link below). We could argue J
by xctr94 3y ago
Progress, the one thing JS has too much of, too quickly, without stabilizing for quality.
There are a number of benefits (see the link below). We could argue JavaScript shouldn’t be isomorphic, as it barely does its job well on either end. Node might in fact be better off without the ‘pollution’ of client-side packages, but well…
https://www.reddit.com/r/node/comments/rby64z/why_esm_what_does_it_solve_for_node_and/ https://www.reddit.com/r/node/comments/rby64z/why_esm_what_d...
- imbnwa 3y agoThing is, Browser JavaScript projects tend to implicitly rely on CJS hacks, such as Jest, as the article points out, or, and correct if I'm wrong, most popular HRM implementations.
- marcosdumay 3y ago> Progress It's lack of quality. When you have a badly designed layer, you have a lot of problems to progress over. And each bit of progress creates a whole lot of new problems you can solve with further progress.