[priansh]

We tried it for a couple months, it was basically a huge hassle getting our stuff to work especially anything that has bindings to CPP (any of the node gyp packages). Also felt like we were putting in a lot more effort to try to get packages with docs for node to work similarly in deno, and weren’t really feeling any value from using deno over node.

If you’re a hobbyist or an academic or starting a totally new project that won’t have dependencies/doesn’t need a large community of modules, then I recommend deno. Otherwise I highly recommend sticking to node until deno comes out with something to make the switch more appealing.

[vorticalbox]

I honestly think the switch (being getting node libraries working in deno) won't happen.

I believe it will be a much better if the community puts time into making a larger module pool that is upto the standard of node

[hardwaregeek]

Yeah I wonder how this will work long-term. I haven't heard of an ecosystem where they successfully avoided packages. Eventually you need some way of pulling in code that's versioned and has versioned dependencies of its own. Otherwise you end up with implicit versions or rolling your own everything, both of which are less than ideal and not necessarily better than packages. Deno could keep adding stuff to its standard library but I doubt even the largest stdlib could fit all users' needs.

[IggleSniggle]

I agree with this entirely. I would absolutely use deno to teach js/ts. I would absolutely use deno in a hobby project. I would absolutely use deno if my requirements were such that I wanted to minimize js dependencies.

[nobleach]

I use when doing DSA/Algorithmic puzzle solving. I typically would use Java for such a thing. TS is pretty nice and when I don't need dependencies.... deno is a nice Typescript first language/runtime/env.