←back to thread

Deno 2.4

(deno.com)
133 points hackandthink | 8 comments | | HN request time: 1.681s | source | bottom
Show context
voat ◴[] No.44488607[source]
People underestimate the node compatibility that Deno offers. I think the compat env variable will do a lot of adoption. Maybe a denon command or something could enable it automatically? Idk.
replies(1): >>44489197 #
1. CuriouslyC ◴[] No.44489197[source]
Honestly, I was bullish on Deno back in the day, but I don't see why I'd use it over Bun now.
replies(2): >>44489615 #>>44489945 #
2. jitl ◴[] No.44489615[source]
Less segfault, improved security / capability model
replies(3): >>44489907 #>>44490207 #>>44490689 #
3. spiffytech ◴[] No.44489907[source]
As a Bun user I don't really get segfaults anymore.
replies(3): >>44489990 #>>44490427 #>>44493716 #
4. pjmlp ◴[] No.44489945[source]
I have yet no reason to fight IT and architects for having anything besides node on CI/CD pipelines and base images for containers.
5. fleetfox ◴[] No.44489990{3}[source]
https://github.com/oven-sh/bun/issues?q=is%3Aissue%20state%3...
6. tmikaeld ◴[] No.44490207[source]
The security model is very underestimated imo, it will be very evident when more bun projects reach production and not experimental.
7. surajrmal ◴[] No.44490427{3}[source]
I've written C for years. The only time it is safe from crashes is when the code doesn't churn and has consistent timing between threads. bun has constant feature churn and new hardware it runs on all the time providing novel timings. It is very unlikely going to be crash free any time soon.
8. drewbitt ◴[] No.44493716{3}[source]
Just got one today! But yes it is better.