Rust is C++ with nanny nags, and immature libraries, and a lot of improvements that 30+ years of C++ has made obvious today which weren’t so obvious back then.
The worst thing about Rust, from my perspective, is that it really seems to push programmers to “multithread all the things” because Rust offers the delusion that you can do that more safely now. Newsflash: all the things do not need to be multithreaded, there’s an awful lot of code that’s just peachy in a single threaded implementation, thank you very much, and multithreading it is just inviting trouble for no significant gains.
Mostly, a good library on C++ (Qt used to be one of those, but it’s started becoming annoying in the past few years) offers a lot of what Rust enforces at the language level. Stick to the library implementations and you’re safe. Color outside the lines when the library isn’t up to what you need - but do so carefully.
Newsflash: all the things do not need to be multithreaded, there’s an awful lot of code that’s just peachy in a single threaded implementation, thank you very much, and multithreading it is just inviting trouble for no significant gains.
I am waiting for your single-threaded fork of the Linux kernel.
What’s a rust programmer? Someone who’s ever written anything in it? If the same holds true for C, probably a higher percentage than of ‘C programmers’ given how long that’s been a teaching language lol
Rust would be better if the rust community wasn’t so up everyone’s ass about using rust.
Attacking the messenger because you don’t have any good argument against the message?
This is the Linux kernel project, one of the technically most conservative projects in the FLOSS community.
Rust is C++ with nanny nags, and immature libraries, and a lot of improvements that 30+ years of C++ has made obvious today which weren’t so obvious back then.
The worst thing about Rust, from my perspective, is that it really seems to push programmers to “multithread all the things” because Rust offers the delusion that you can do that more safely now. Newsflash: all the things do not need to be multithreaded, there’s an awful lot of code that’s just peachy in a single threaded implementation, thank you very much, and multithreading it is just inviting trouble for no significant gains.
Mostly, a good library on C++ (Qt used to be one of those, but it’s started becoming annoying in the past few years) offers a lot of what Rust enforces at the language level. Stick to the library implementations and you’re safe. Color outside the lines when the library isn’t up to what you need - but do so carefully.
I am waiting for your single-threaded fork of the Linux kernel.
What percentage of Rust programmers contribute to the Linux kernel?
What’s a rust programmer? Someone who’s ever written anything in it? If the same holds true for C, probably a higher percentage than of ‘C programmers’ given how long that’s been a teaching language lol
Well, academic exercises for grades, I’d call Rust students.
Throw away programs people do for fun, I’d call Rust hobbyists.
Pretty much anyone else, doing it for money (a living: roof over head, food on table), or open source contribution - I think they qualify.