News for hackers. Stuff that matters.

A comment on Deno v1.27. Parent comment

Re:Deno v1.27 by brundolf on Thursday October 27, 2022 @05:39PM (#33364396)
I see NPM compatibility as a temporary stopgap. They tried to make a hard break all at once, and then Bun made it clear that no, actually people still really want access to that existing ecosystem for now.

But new code written for Deno starts out on that better foundation without CommonJS, several different module-resolution algorithms, manual transpilation, competing linting and testing standards, etc etc. They just need to bridge the gap in the meantime, until Deno's own ecosystem gets more filled out. That's the dream anyway.

[ Parent | on HN ]
Re:Deno v1.27 by SOLAR_FIELDS on Thursday October 27, 2022 @09:49PM (#33366547)
The pedigree of Deno does speak for at least something as well. Who better to address the flaws of a lasting project someone created than the creator themselves? Just from incentive alignment it’s a powerful motivator.
[ Parent | on HN ]