4 ms·
I can speak to this since I've used Deno quite a bit. The problem is that the Deno ecosystem is, unfortunately, still very young. This young age also brings a l
by dimgl 4y ago
I can speak to this since I've used Deno quite a bit. The problem is that the Deno ecosystem is, unfortunately, still very young. This young age also brings a lot of instability with it. On the other hand, the Node ecosystem is extremely mature. There's a lot of legitimately great npm packages with years of development and bug fixes.
Not being able to use these packages is a detriment to Deno's adoption, not a boon. IMO, the biggest issue with Node is Node itself, not its ecosystem. All Deno does is bring the JavaScript ecosystem to a more modern standard. Being able to pick and choose the npm packages you want to use while slowly adopting the Deno stdlib and Deno specific packages will make it easier for developers to make the switch.
Once Deno ships these features I'll try Deno again. Right now I'm really turned off by JavaScript development. The last couple of times I've tried to start up a project on Node it's been an absolute nightmare with its ESM madness and lack of TypeScript support. On the other hand, getting started with Deno was a breath of fresh air... up until the real development starts.
- nobleach 4y agoThis was my experience as well. When Fresh dropped a few weeks/months ago, I thought, "oh neat, islands architecture, that's right up my alley". I decided just to blindly fool around with it one weekend. I immediately was hit with, "but what do I do with my styles? How can I transform all this ancient Less into CSS and attach it to files/components?" I'm sure there's some sort of way around all that but, right now it seems like I'd need to have a node instance just to do a compilation step!
- Rezwoodly 4y agoHow is Nodes biggest issue, Node? It eclipses any other JS runtime out there, and by a long way
- dimgl 4y agoNode ESM support REALLY sucks. Node import maps suck (and are poorly documented). Node doesn't support TypeScript out of the box. Node dependency management has always sucked. I've used three different package managers, and I'm sure more will pop up in the future. I've always loved Node.js. But the unfortunate reality is it sucks to build new projects in it in 2022.
- qbasic_forever 4y agoTotally agree on ESM supporting being a mess. We're going to see projects littered with .mjs files for decades to come. People will whisper in hushed tones.. what the heck is a mjs file, isn't this just javascript? Why did we do this again? No one will remember.