Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I think Deno's management have been somewhat distracted by their ongoing lawsuits with Oracle over the release of the Javascript trademark.

I started out with Deno and when I discovered Bun, I pivoted. Personally I don't need the NodeJS/NPM compatability. Wish there was a Bun-lite which was freed of the backward compatability.



Ironically, this was early Deno - but then adoption required backwards compatibility.


I'm in a similar position.

I use Hono, Zod, and Drizzle which AFAIK don't need Node compat.

IIRC I've only used Node compat once to delete a folder recursively with rm.


In regards to Deno, to me that means their business is not really flying and they need this kind of distractions instead.

Amount of people at big corps that care about their lawsuit, and would switch their IT guidelines from node to Deno due to such heroic efforts?

Zero.


What do you dislike about having node compatibility?


The bloat. I prefer lean designs with plug-in modules for additional functionality. Not only do unused sub-systems take up memory, but they also increase the potential attack surface.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: