Remix.run Logo
▲ the__alchemist 17 hours ago

My take too. (Aside from this being a well-written, clear article, that I think highlighted a fair selection of relevant points; especially the "always use uint8_t instead if int" part).

I don't see rust a "memory safe" language, or a niche one. I have complaints about it etc, but it's overall a fair baseline of reasonable decisions. When I look at C or other languages rust has learned from, I have more "Yikes, that's rough" takes. So... rust as the language of least "fucked up", to use your phrase? Ownership/safety are one part of the picture, but not what defines it for me.

▲cohani 17 hours ago | parent [-]

[flagged]

▲the__alchemist 15 hours ago | parent | next [-]

Is this the sort of thing you only need to know about if building/maintaining compilers? I ask because I don't know what that means from a practical perspective. I'm familiar with Ferrous systems from their work on probe-rs, defmt, and flip-link, which are exquisite libraries / tools.

edit: I think this is a bot or troll account.

▲Ygg2 16 hours ago | parent | prev [-]

Rust never had a goal of having well defined spec. It all depends on what ecosystem wants.

In lieu of that it didn't fuck up.