4 ms·
>Deno to easily import npm packages and make 80-90% of npm packages work in Deno within the next three months. I get it, I understand it, but it is depressing
by 999900000999 4y ago
>Deno to easily import npm packages and make 80-90% of npm packages work in Deno within the next three months.
I get it, I understand it, but it is depressing to know that we're going to be dealing with horribly ridden legacy NPM code for the next 800 years.
A lot of the code on NPM is just bad. And now we're going to keep this legacy of just, bad JavaScript .
This is why I prefer dart and flutter for making mobile apps. Over react native.
- tomphoolery 4y agoThere's a lot of code on NPM in general, and while there's definitely a lot of warts, there's a lot of good code on there as well. It makes no sense to write off an entire package ecosystem just because some of the packages are unmaintained or poorly written. Plenty of NPM packages are useful beyond the JS ecosystem, and I think until you get a better and more reliable system for distributing those packages, NPM is probably going to be here to stay, like it or not.
- oefrha 4y agoThe Deno/npm incompatibility up till now means a good number of popular and semi-popular npm packages got a shoddy Deno port done by someone a year ago, then never updated again. That is to say, legacy code got even more legacy.
- qbasic_forever 4y agoDeno still has a great standard library, so there's much less need to pull in crufty little packages to do simple tasks. IMHO the npm support in deno is more for pulling in the big packages like wrappers around databases or services and such which haven't yet written or want to write a deno-specific version. Sure you can still pull in junk like left-pad, but you don't need to do that.