Comment by GianFabien

Comment by GianFabien 15 hours ago

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.

pjmlp 5 hours ago

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.

Reply View 0 replies

carefulfungi 13 hours ago

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

Reply View 0 replies

pier25 15 hours ago

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.

Reply View 0 replies

Zambyte 13 hours ago

What do you dislike about having node compatibility?

Reply View 1 reply

GianFabien 7 hours ago

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.

Reply View | 0 replies