← Back to context Comment by tomjakubowski 1 day ago I doubt it would work out. The engineering cultures could not be any different. 2 comments tomjakubowski Reply 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 2 hours 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 2 hours 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 2 hours 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.
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.