For the people discussing the merits of functional programming in this quote-voting topic, discourse has a wonderful function: "reply as new topic".
It hides under the post date in the top right ("3h") -> "+ new topic".
Let's try to keep this thread on-topic, and follow-up on the (admittedly cool) tangents elsewhere.
To quote from our very own forum faq:
Keep It Tidy
Make the effort to put things in the right place, so that we can spend more time discussing and less cleaning up. So:
• Don’t divert a topic by changing it midstream.
I don’t like Rust being pigeon holed as a “safer C++”—it’s so much more than that.
Slightly off-topic, but I've had the experience in the exact opposite direction: having written lots of C++ and having been constantly looking for improvements and patterns that ensure safety, Rust had basically no learning curve for me.
As the intern honestly admits in that blog, most users of high level languages have no idea where the memory is they are using and who else is using it. It's not something they think about until they get the segfaults and corrupt data.
Memory in C++ is a leaky abstraction (see what I did there )
I came from C# where I found that low level memory things were kind of swept under the rug and left to the compiler to deal with. These kinds of things interested me so I tried C++. To put it simply, I was not prepared to deal with C++, so I instead switched to Rust, and have found that dealing with the details of low level things can be nice and refreshing little niches, opposite to my experience in C++ and present compared to C# (At least at the time and my understanding of it).