Follow

@daridrea Most of the programming I've done in Cpp was C++ 11. I often would write the same program in C just because one was more fun to use.

I believe it was C++ 17 or 20 where I tried to use it and it felt so very wrong. A language that I used became unusable to me. Except for the embedded versions, I don't see myself using Cpp again.

Rust looks beautiful and the memory safety wasn't the main reason I wanted to learn it. It should have a bright future if the foundation doesn't get in the way.

C is C. It's a great language that can look like an affront to the gods but run reliably.

To me it appears that computer architectures are converging with some of the newer languages. Java used to be a joke for performance and then Android arrived. Java could then be used in a severely mutilated form and produce code that had respectable performance.

It's not too much of a logical stretch to say that similar architectural changes could be in the works. Changes that would allow for better memory safety and utility with Rust and similar languages but using ISA. One does have to justify at least some of the backdoor embedded processors. Support the anemic ARM cores with a strong CPLD and the memory safety model could go from code through the OS and be handled by the CPU.

Sign in to participate in the conversation
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.