2 ms·
The problem with Deno is that it has lost the plot. When it was first announced years ago, it was simply a safer, faster JS/TS runtime “written in Rust” which I
by yahoozoo 1y ago
The problem with Deno is that it has lost the plot. When it was first announced years ago, it was simply a safer, faster JS/TS runtime “written in Rust” which I assume it still is but now you go to the website and you click a “Products” drop down containing a bunch of other shit.
It’s like they looked at what Vercel did with introducing a deployment platform after their initial NextJS work and wanted to follow suit.
- bredren 1y agoWas it this or did the JavaScript / node communities get their acts together? I had thought a lot of what Deno was setting out to do was cool beans for a time but parity was faster to come from js/node than expected.