Re:BleedingTooth: Linux Bluetooth Zero-Click Remote Code Exe...
by anaganisk on Thursday April 08, 2021 @11:50AM
(#26740263)
I think now I see the presence of Rust Evangelism Strike Force, seriously I see these "C cringe" comments 6 times today In less than an hour.
Re:BleedingTooth: Linux Bluetooth Zero-Click Remote Code Exe...
by tediousdemise on Thursday April 08, 2021 @12:12PM
(#26740543)
Probably at around the same frequency that developers of yesteryear saw “FORTRAN cringe” comments, if I had to reckon.
Re:BleedingTooth: Linux Bluetooth Zero-Click Remote Code Exe...
by 4fips on Thursday April 08, 2021 @08:48AM
(#26738056)
At least C is a complete language and a solid building block which is possible to reason about, compared to C++ which is becoming more and more bloated in a modernization attempt, so C++ projects need to be constantly updated and rewritten to catch up, which rarely happens in practise. On the other end, C++ can hardly adopt things like memory model based on Rust's borrow checker, so in this regard C++ is a dead end.
Re:BleedingTooth: Linux Bluetooth Zero-Click Remote Code Exe...
by tediousdemise on Thursday April 08, 2021 @09:03AM
(#26738182)
In my mind, C++ is one of the only languages that is evolving with the times.
They don’t add features that break backward compatibility, or features that sacrifice runtime performance especially if you don’t use those features. Most new features added to C++ are actually just additions to the STL, which you aren’t forced to use.
It is an open standard, so there is plentiful competition in the realm of compilers. Rust only has 1 so you are SOL if you don’t like something or if the project goes bust one day.
Re:BleedingTooth: Linux Bluetooth Zero-Click Remote Code Exe...
by 0xdeaddeaf on Thursday April 08, 2021 @08:13AM
(#26737763)
You may think putting C++ and Rust in the same category against C will make your comment a bit more popular. But the reality is Rust people cringe at C++ code a lot more.
The code is an utter shitshow, inviting disaster through seemingly normal use of the language. It contains a mess of malpractices that make any modern C++ or Rust developer cringe: goto, memcpy, naked pointers, type unsafe casts, raw loops, using malloc to allocate memory for input buffers.
Why do people continue to juggle chainsaws? I think it's fear of new things, fear of change. Old habits die hard.