To me it seems that those "bad decisions" that Ryan regrets while he was designing Node.js are a tad overblown. I mean, I've seen the list of "huge improvements" of Deno compared to Node but I have to say I'm underwhelmed.
At its core Deno is still V8, so performance is probably identical to Node ... then we're throwing away the complete ecosystem around Node.js (as you rightly say, the lack of npm and package.json isn't really a pro, rather a con), plus the need to relearn everything.
So I'd say this does not look like the "revolution" we've been waiting for. It's cool as a toy to play around with and maybe for a few non-critical and small "greenfield" projects, but beyond that I'd say let it mature for a few years and then we'll see again.
True, I agree with you! It all makes sense if we see the bigger picture. Deno is essentially node with tiny bit improvements, but things like not supporting NPM libraries at the moment are hinderance to using them right now in 2020.
To me it seems that those "bad decisions" that Ryan regrets while he was designing Node.js are a tad overblown. I mean, I've seen the list of "huge improvements" of Deno compared to Node but I have to say I'm underwhelmed.
At its core Deno is still V8, so performance is probably identical to Node ... then we're throwing away the complete ecosystem around Node.js (as you rightly say, the lack of npm and package.json isn't really a pro, rather a con), plus the need to relearn everything.
So I'd say this does not look like the "revolution" we've been waiting for. It's cool as a toy to play around with and maybe for a few non-critical and small "greenfield" projects, but beyond that I'd say let it mature for a few years and then we'll see again.
True, I agree with you! It all makes sense if we see the bigger picture. Deno is essentially node with tiny bit improvements, but things like not supporting NPM libraries at the moment are hinderance to using them right now in 2020.
Right ... it's an evolution, not a revolution.