> it just lets you do it in a more performant way. That's not necessarily true. It lets you do it without a tracing GC, which is marketing genius. Whether or n

> it just lets you do it in a more performant way. That's not necessarily true. It lets you do it without a tracing GC, which is marketing genius. Whether or not it's more performant depends. A lot. > It enforces rules around mutability These are more needed due to achieving memory safety in the absence of a tracing GC. I like its rules for this; I'm just saying that they're a necessary consequence. > and handling errors I prefer exceptions myself. But one can write library types that force the user to handle error cases in other languages. It's not as nice as when sum type support is baked in, of course.