>>105631173>Rust isn't OOPneither is modern c++. the "object orientation" facilities of c++ are covered in cobwebs.
anyways it's irrelevant. rust and sepples are both maximalist takes on systems programming. c is not. you're getting too caught up in surface-level observations of both.
>in the sense of actually prototyping, quickly building a proof-of-concept.sepples is terrible for rapid prototyping.
>Neither is memory safety even thaaat important where you use c++that's not at all tied to the language, it's tied to the domain.
i think memory safety is pretty fucking important for microsoft's nt kernel, for the f35, etc.
on top of that, it's just weird to bring it up because it's the one thing rust uses to differentiate itself. it's what they went all in on after the 2011 paradigm shift, but you know, there's the entire rest of the language.
yes you can argue there are still reasons to use rust, but then you're still left with something that lifts 95% of its syntax from sepples which is really bad at expressing those ideas. that's why you have to wrap polymorphic types in <>, use :: for namespaces, ownership semantics, etc.
honestly i'd be more inclined to use rust if they kept the ML heritage. i DON'T want a fucking maximalist pseudo-sepples. give me SML with pointers, explicit allocation, no gc, etc. if it has an affine type system on top of that, great. if not, i don't care.
i don't want to use this ugly piece of shit maximalism. i've got 500k lines in c++ and it sucks. it fucking sucks. not because of a lack of memory safety or whatever, but because this kind of grammatical schizophrenia and overburdened featureset makes using the language a royal pain in the fucking ass. not just to write, but also to read. c is downright pleasant compared::to::namespace::soup.unrwrap_or(32.transmute()).exit<kill::myself>()::{?} and c's only good trait is how easy it is to write a basic compiler for it.