If you take a look at their repo there's currently 608 issues and 60 open PRs. Lots of work to be done. It looks like they're focusing on that rather than the UX. If you look throughout the various repos under denoland you will see there are many roadmaps still in their early stages. Once these are addressed to a more reasonable degree I'm sure teams and companies will take a risk on deno, with or without NPM compatibility.
I'd like to see deno become robust and intuitive enough to outlive node by a longshot.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Ryan living in 2030+
If you take a look at their repo there's currently 608 issues and 60 open PRs. Lots of work to be done. It looks like they're focusing on that rather than the UX. If you look throughout the various repos under
denoland
you will see there are many roadmaps still in their early stages. Once these are addressed to a more reasonable degree I'm sure teams and companies will take a risk on deno, with or without NPM compatibility.I'd like to see deno become robust and intuitive enough to outlive node by a longshot.