3 ms·
I wonder if Bun will end up being something that will eventually drive the innovation within Node.js, and maybe even merge with it (remember io.js?)
by yanis_t 3y ago
I wonder if Bun will end up being something that will eventually drive the innovation within Node.js, and maybe even merge with it (remember io.js?)
- re-thc 3y ago> and maybe even merge with it (remember io.js?) Not likely. Bun doesn't use v8. And if Bun has to go the way of NodeJs nothing will likely happen as well. Bun can move fast because there aren't as many stakeholders, committees and all sorts of gatekeepers in the way.
- iddan 3y agoProbably won’t merge because it’s a VC backed project
- joshxyz 3y agoi doubt it will get merged. nodejs devs are firm on "this proposal is betteer kept in userland than within nodejs" approach, which also kept their ecosystem stable and predictable at most times.
- akmittal 3y agoI don't think it will merge. After deno nodejs is getting similar features like native fetch, web stream etc. Similarly nodejs can just implement buns unique features
- intelVISA 3y agoI hope so, whilst Bun isn't the fastest in this space it's definitely got potential to be if they can get some talented SWEs behind it.
- manojlds 3y agoIo.js was a fork of Node right. A merge is not on cards here.
- afavour 3y agoI can’t imagine a merge ever being on the cards. io.js was a fork of Node so merging it back in was a relatively simple proposition. Bun uses an entirely different JS engine so a merge would be horrendous, it would be more like a ground up rebuild. I’m also still a little lost on the “why” of Bun. I respect the tech a ton having noodled around with the JavaScriptCore API myself in the past. But I’m not sure why I’d use it over Node.