Comment by nailer 1 day ago (thinking emoji) they could merge.Seriously, they're both Rust now. They share goals. 4 comments nailer Reply tomjakubowski 1 day ago I doubt it would work out. The engineering cultures could not be any different. sysguest 1 day ago well bun could 'gradually become deno':1. add 'enhanced security mode' that's actually 'deno-compatible/like' (permissions, etc)2. mark libs/executables/etc as 'enhanced security compatible'3. ...merge by buying out deno? andrewflnr 27 minutes ago > The engineering cultures could not be any different.A Bun team willing and able to execute your plan is not one willing to merge a vibe-coded rewrite in a couple weeks. notnullorvoid 1 day ago They may share some goals, but also have differing and opposing goals.But it's possible that all 3 Deno, Node, and Bun could share some code in the future considering they now all require Rust as part of their build process.
tomjakubowski 1 day ago I doubt it would work out. The engineering cultures could not be any different. sysguest 1 day ago well bun could 'gradually become deno':1. add 'enhanced security mode' that's actually 'deno-compatible/like' (permissions, etc)2. mark libs/executables/etc as 'enhanced security compatible'3. ...merge by buying out deno? andrewflnr 27 minutes ago > The engineering cultures could not be any different.A Bun team willing and able to execute your plan is not one willing to merge a vibe-coded rewrite in a couple weeks.
sysguest 1 day ago well bun could 'gradually become deno':1. add 'enhanced security mode' that's actually 'deno-compatible/like' (permissions, etc)2. mark libs/executables/etc as 'enhanced security compatible'3. ...merge by buying out deno? andrewflnr 27 minutes ago > The engineering cultures could not be any different.A Bun team willing and able to execute your plan is not one willing to merge a vibe-coded rewrite in a couple weeks.
andrewflnr 27 minutes ago > The engineering cultures could not be any different.A Bun team willing and able to execute your plan is not one willing to merge a vibe-coded rewrite in a couple weeks.
notnullorvoid 1 day ago They may share some goals, but also have differing and opposing goals.But it's possible that all 3 Deno, Node, and Bun could share some code in the future considering they now all require Rust as part of their build process.
I doubt it would work out. The engineering cultures could not be any different.
well bun could 'gradually become deno':
1. add 'enhanced security mode' that's actually 'deno-compatible/like' (permissions, etc)
2. mark libs/executables/etc as 'enhanced security compatible'
3. ...merge by buying out deno?
> The engineering cultures could not be any different.
A Bun team willing and able to execute your plan is not one willing to merge a vibe-coded rewrite in a couple weeks.
They may share some goals, but also have differing and opposing goals.
But it's possible that all 3 Deno, Node, and Bun could share some code in the future considering they now all require Rust as part of their build process.