Here we go again, making the same mistake. I'm constantly reminded that every 5 years the amount of... Tagged with bunjs, javascript, node, npm.

Dev.to is a community platform for developers, offering resources, discussions, and networking opportunities to empower individuals in their coding journey. Developers can learn new programming languages, frameworks, and tools, engage in discussions on best practices, and share their experiences with fellow developers to enhance their skills and grow their professional network.

Yarn and Bun went off to create their own competing technology. Both sold themselves on being way faster. Both went in with the goal of splitting the ecosystem. Both announced that they were officially v1.0 and ready for production!...while not actually supporting Windows. In 2023, npm is still faster than Yarn.

Bun hype. How we learned nothing from Yarn

Part Five - My predictions for the future

Finally, someone is talking about the ‘I made the same thing but better instead of contributing to the project I copied from’ syndrome JS community has. It’s OK to have different options to choose from but there’s not much benefit from reinventing the wheel instead of focusing on improving what we already have

TLDR;
<ul>
<li>Bun focuses on too much things. It will become exponentially harder to maintain all this and adopt new features from (Vite, Jest, TS, TSX, etc)</li>
<li>Node.js will take notes and adopt these diffs (like cjs, es mixed imports) and speed. [ Opinion: Maybe even an interchangeable runtime (V8, JavascriptCore) ]</li>
</ul>

While I believe being warry of any new hyped technology. I don’t think the comparison is fair, to either Bun or Yarn.
On not being able to run yarn with monorepos in Windows, I’ve never had this problem and I’ve used every OS under the sun. Hell in my current project I use EndevourOS (linux), 2 other use Mac and one guy uses Windows. Our monorepo suddenly stopped working with npm, and low and behold yarn was the solution for everyone.
It’s also crazy to say Bun is marketing themselves has production ready, since it’s actually hard to deploy it for most developers without DevOps knowledge. And Bun has acknowledged this has being a runtime for fun only has of now.
On the internet all is lost, nothing is forgotten. Here you go MeteorJS 2014 documentation: <a href="https://web.archive.org/web/20140123005045/http://docs.meteor.com/" target="_blank" rel="noopener nofollow">https://web.archive.org/web/20140123005045/http://docs.meteor.com/</a>
Everything else I think it’s a fair point on being warry of Bun.

I wished Deno would get more support, I guess noone like <code>node_modules</code> and I guess it would be easier to get rid of that. Also, typescript of course.
It seems that a lot of runtime remakes or remakes in general just cut corners and users are left with having the amazing speed only in some edge cases and in other cases can’t even make it run at all. Harsh trade-off.

i got excited because fast.
i got sad because no windows support (i dont want to use WSL).
i got excited again because cloudflare pages supports it.
i got sad again because of this post.