DEV Community

Discussion on: Reasons I'll never use Deno

Collapse
 
leob profile image
leob • Edited

I'm also not convinced, neither by TS nor by Deno.

The problem I see with Deno is that it's yet another distraction and yet another bandwagon that people are jumping on and wasting time on.

From what I've seen, Deno isn't advancing the "state of the art". The decision to dump package.json and simply use "import" to pull in all of your dependencies (and then having to use an ugly URL syntax if you want to specify versions) seems a step back. Npm, Yarn, package.json and so on are useful tools and proven technology, why throw it out the window and reinvent the wheel?

Most of all, I just see it as a distraction and a waste of time, which takes away people's focus from doing useful things. It's yet another toy to play around with, to learn the ins and outs of, and to waste time on instead of doing something productive (as in, create apps or useful software).

Less is more. Enough is enough. We don't need yet another way to do essentially the same thing.

Hats off and kudos big time to Ryan for inventing Node.js, but no I don't see the point of Deno.

Collapse
 
4r7d3c0 profile image
4r7d3c0 • Edited

If there's something new to invest time to learning, then it's only Dart and Flutter (or Go, but it doesn't have the web app framework like Flutter, not that I know of).

Collapse
 
leob profile image
leob

You're right ... Rust is also a good one