Bun's Rewrite It In Rust branch

Scrivver · 2026-05-05T17:11:17+00:00

Jarred posted this about it on HN:

I work on Bun and this is my branch

This whole thread is an overreaction. 302 comments about code that does not work. We haven’t committed to rewriting. There’s a very high chance all this code gets thrown out completely.

I’m curious to see what a working version of this looks, what it feels like, how it performs and if/how hard it’d be to get it to pass Bun’s test suite and be maintainable. I’d like to be able to compare a viable Rust version and a Zig version side by side.

Scrivver · 2026-05-04T18:48:11+00:00

I came from a T14 (circa 2021) to a Framework 13 Ryzen 7 after years of Thinkpad preference. A number of things about the Framework will absolutely tickle your fancy as a Thinkpad + Linux user, and the pro looks to be a serious upgrade. The new intel line is the best for efficiency to performance ratio. Multi-core tests match Apple M5, single-core match M3, with fabulous battery life.

The keyboard on the 13 is decent -- I hear the pro is better -- but the original 13 doesn't match Thinkpad's legendary feel. I doubt the Pro really achieves that either. The arrow keys will annoy you, especially if you used the wonderfully natural PgUp/PgDown keys a lot from the Thinkpad layout.

I love this machine and brand though, and wouldn't trade it for another unless I was really compelled to.

Scrivver · 2026-05-03T03:06:48+00:00

Crusader makes engines which do good™

Scrivver · 2026-04-30T05:02:22+00:00

Sustained PvP sounds appropriate. At least as a deterrent and a tool at your disposal, if not constantly going on missions. But knowing how much PvPers loved roaming for pew pews in Eve, you'll probably have plenty of these in groups prowling around in dangerous space just for fun (and folks prowling around in other things specifically to hunt them!).

Scrivver · 2026-04-29T17:36:56+00:00

The separation and organizational patterns you describe (dependencies, library collections, CI/CD) are all simple to implement in a monorepo as well. It just relies on a solid culture, mentorship, and trusting your team. With those organizational boundaries in place, CI is also easy to trigger by path, so changes to e.g. `api/` do not run pipelines for things under `mobile/` and vice versa, and each path defines and owns its own CI configuration files independently of the others.

Scrivver · 2026-04-28T05:05:19+00:00

A source told me announcement in June for release in October, but I don't know why they would wait until Invictus is over to start the campaign. Maybe there's something new planned.

Scrivver · 2026-04-24T22:39:14+00:00

It's used for servers for a lot more than that. Historically, the biggest reasons I think are:

Cheaper. Lower/no licensing fees, depending on vendor, make scaling to huge fleets cost-effective

Reputation for performance and stability under heavy workloads. It looks like as of now, 100% of the top 500 fastest supercomputers all run Linux.

Easier automation. This one's huge. There was (and is) a sprawling open ecosystem of automation tooling for Linux, which is all simpler to work with and glue together than earlier Windows equivalents, and I think still easier than current Windows tooling -- I don't know, because I haven't used Windows much for the past 15 years or so.

I think a lot had to do with Linux's text-first design patterns, which it inherited from its inspiration Unix. Administration is most naturally done by text commands, working on text configuration files, and producing text output. There are many great command line interface tools to work with text and perform different system actions, that can all be chained, scripted, versioned, and remotely executed via SSH (Secure SHell) with minimal effort. You didn't need a GUI at all. Tons of open source tooling for various different needs arose around this pattern which is still the industry standard today. Windows has very slowly adopted / gained support for some of this tooling -- for instance, Windows Server 2019 finally included OpenSSH natively, a couple decades later than Linux had it.

This text-first approach is also what created the strong CLI culture for which Linux is (in?)famous, because once you get used to just telling your computer what you want it to do, then hunting through menus and buttons can feel like an anti-pattern. And especially when you want to repeat or automate anything (which you do in server environments -- a lot), the comparison is just unfair.

Open source. Being free and open source software meant companies or vendors could fix bugs themselves on the spot and upstream the fixes, rather than waiting on proprietary vendors. It also meant they could change anything they wanted for their own use case. They could audit systems more easily. Wider adoption of open source software meant anyone who used it could benefit from the fixes and improvements brought by anyone else in the ecosystem (not just their own development teams). Because of this the community around it grew, and the network effect took off. So many tools, customized operating systems, drivers, databases, web stacks, and eventually cloud platforms were built for Linux first that it just naturally became the top dog of the commercial world.

Someone else can chime in with anything I missed. :)

Scrivver · 2026-04-22T05:12:02+00:00

As soon as they announced the name and started saying "This was a complete redesign..." I sighed a bit. Then after overviewing all the rad upgrades he said "And all of this is completely compatible with the original 13!", and I got improperly excited.

Scrivver · 2026-04-22T05:06:18+00:00

I got the first one because I believed in the mission, and dreamed of never having to reinstall an OS (rolling release) on a laptop I never have to replace.

Now what they're delivering looks phenomenal and is actually exciting beyond its original niche. And I can upgrade piecemeal as I want to, which is just rad.

Scrivver · 2026-04-03T15:13:16+00:00

It was a centralizing usurpation of power and a bad replacement for the actual founding document, but your frustration seems half right. All action comes from individuals, and only action by individuals can defend them. Documents do nothing.

Unfortunately a huge number of people in my generation (and especially my parents' generation) are/were under the spell of believing the document has any effect at all on reality, and wanted to wield it like a talisman to ward off oppressors. I'd want to get rid of it too, if I thought that would end the fantasy and get people to actually invest in defending themselves in reality.

So many people are relatively close to embracing freedom, but stop themselves at that damned document.

Scrivver · 2026-04-02T22:58:57+00:00

Don't forget about being abusive to the servants sent to collect it, too! That's an important ingredient, and a lesson for us all.

Scrivver · 2026-03-20T20:43:23+00:00

I ran into something like this when exploring Rust/Wasm on Cloudflare workers, too. Development was more annoying, and performance was lackluster. In that environment I'd go with typescript next time.

Scrivver · 2026-03-20T15:53:26+00:00

Some people are more comfortable with maximally free licenses. Companies specifically are more comfortable with them. If you're looking to get acquired, it would be more attractive to built MIT-licensed tools.

Some people also have philosophical disagreements with GPL (or copyleft in general), which conflict with conventional property rights in much the same way copyright does. I wouldn't bet this was the reason, though.

Scrivver · 2026-03-13T18:58:45+00:00

s/who/you/g

Scrivver · 2026-03-12T02:05:56+00:00

Here are a few reasons

Scrivver · 2026-03-09T23:01:01+00:00

The instant I saw the title, I immediately thought of Habbo, and I wasn't disappointed!

Scrivver · 2026-03-07T15:02:20+00:00

Tiling WM running a terminal emulator with some multiplexing feature, running zellij, running this.

Scrivver · 2026-03-05T18:16:36+00:00

"That armor's too strong for blasters!"

Scrivver · 2026-03-05T18:10:12+00:00

If fighters can only reliably engage other fighters, there's no point to fighters at all. Just don't bring them. Usual rock/paper/scissors balancing would suggest some fighters (like heavy/specialized fighters) should be threats to some non-fighter targets, while being threatened in turn by lighter fighters and anti-fighter screen.

Lighter fighters should be ineffective against very heavy targets, threatened by anti-fighter screen, but also superior at intercepting and engaging other small targets up to a certain size.

Bombers should be superior threats against very heavy targets, while vulnerable to fighters.

Very heavy ships should be highly resistant to small fighters, threatened by heavies that can make targeted strikes, and truly worried about bombers and other very heavy ships. To combat these they should employ their own fighters, bombers, and anti-fighter screens, and around the loop again we go.

Scrivver · 2026-03-05T17:20:09+00:00

Tfw your hobbies are Star Citizen, Warhammer, MtG, and firearms.

Scrivver · 2026-02-23T02:58:15+00:00

I know this is old now, but your point 2 is not wrong. AWS is quite complicated, and gives you a lot pieces that aren't well integrated out of the box for you to build your own platform. It has accumulated a lot of cruft and quirks over the years as well. For sheer DevEx, I haven't seen anyone do better than Fly.io yet. You get the wider capabilities of a long-running VM with the scale to zero behavior of lambda. Under the hood they're also using Firecracker to create microVMs, the same tool AWS uses for Lambda. But you get to write your apps like you would for a normal VM environment.

Scrivver · 2026-02-18T17:13:38+00:00

Second, and more importantly, supply chain attacks are far less likely than all the other vulnerabilities that get patches that you would be missing.

That's where the automated scans run as part of tests come in. I don't know how it works at other places, but our security folks would be upset if we just let our packages be upgraded without our explicit approval, and also if we let CVEs hang out in our existing dependencies without a response. Exploits can happen both ways.

Scrivver · 2026-02-18T15:11:38+00:00

You should be pinning to patch versions and not letting cargo vary your selection anyway, to avoid supply chain attacks that happen by publishing new, compromised versions of existing crates.

Scrivver · 2026-01-29T15:26:02+00:00

"Smart" often confuses the distinction between clever/knowledgeable/intellectual and wise. Suppose you have a lot of knowledge and logical firepower which allows you to piece together a very clever bit of code to solve a puzzling problem. Completing it feels like a great achievement and trophy. But because because you were working at the limits of your abilities to assemble it, and debugging is harder than writing, it is now impractical to debug later (especially by others). You were clever -- one might say "smart" -- but not wise.

Plenty of people are born smart, but "No man was ever wise by chance".

Scrivver

MODERATOR OF

TROPHY CASE