Content added Content deleted
(Created page with "esbuild, which debuted in 202, is an existential threat to the triplescripts.org ecosystem. The esbuild developers are not bad people working for nefarious means. esbuild papers over the NodeJS ecosystems problems. The adoption of esbuild means that many programmers will never shed the fundamental problems inherent to the way the NodeJS community tends to do things, since it also provides friction (in the form of apparent build time regressions) opposing gradual impro...") |
(fix 2020 typo; clarify that existential threat concerns Modern JS) |
||
| Line 1: | Line 1: | ||
esbuild, which debuted in |
esbuild, which debuted in 2020, is an existential threat to the triplescripts.org ecosystem—at least where Modern JS is concerned. The esbuild developers are not bad people working for nefarious means. |
||
esbuild papers over the NodeJS ecosystems problems. The adoption of esbuild means that many programmers will never shed the fundamental problems inherent to the way the NodeJS community tends to do things, since it also provides friction (in the form of apparent build time regressions) opposing gradual improvement. It means NodeJS development is in a sort of gravity well—stuck near a local maximum—like water that is never able to evolve the ability to flow uphill. |
esbuild papers over the NodeJS ecosystems problems. The adoption of esbuild means that many programmers will never shed the fundamental problems inherent to the way the NodeJS community tends to do things, since it also provides friction (in the form of apparent build time regressions) opposing gradual improvement. It means NodeJS development is in a sort of gravity well—stuck near a local maximum—like water that is never able to evolve the ability to flow uphill. |
||
Revision as of 14:43, 17 January 2022
esbuild, which debuted in 2020, is an existential threat to the triplescripts.org ecosystem—at least where Modern JS is concerned. The esbuild developers are not bad people working for nefarious means.
esbuild papers over the NodeJS ecosystems problems. The adoption of esbuild means that many programmers will never shed the fundamental problems inherent to the way the NodeJS community tends to do things, since it also provides friction (in the form of apparent build time regressions) opposing gradual improvement. It means NodeJS development is in a sort of gravity well—stuck near a local maximum—like water that is never able to evolve the ability to flow uphill.