Glad you enjoyed it. 🙂

You missed one use case: entertaining GC developers. We can deduplicate String payload. We *could* canonicalize the String identity as well, but that might accidentally make broken code using == work. And it’s so much more hilarious to eagerly wait for the == to run and inevitably bug out!

Ah so you are approaching this like instrumentation based profiling? I thought you would be the statistical sampling kind of guy.

Sure. What you do is to go to a place full of garbage, evacuate the stuff you care about to a safe place, then nuke the entire place.

We don’t really plan for things to ship at a particular release. We will see how things pan out.

So if I want memory safety in an app, would I be ”just wrong” for thinking it’s easier to get that from a GC compared to a borrow checker?

I don’t know. When I talk to people writing rust for systems programming, they say its lack of ABI and dynamic linking friction makes it a poor choice, but pretty sure it’s good for apps. And the people writing apps say while it’s hard to get things wrong it’s too hard to get anything right.

Another pack here: go.bsky.app/F7m9rBy