The Furries and Big Tech want to force Rust into the Linux Kernel.
(www.youtube.com)
You're viewing a single comment thread. View all comments, or full comment thread.
Comments (51)
sorted by:
I've actually always thought C and C++ was cool because it seems much more intuitive to how data actually works in the computer. Other, more 'modern' languages seem to hide so much of the actual data manipulation that it actually seems to make less sense.
That's because you were taught under the previous paradigm, that understanding the foundations gives you a good way to filter out bad patterns.
Nowadays it's low skill programmers from india and people using AI to cargo cult good practices, and so making it dumb for them means more code gets written, which managers like, because they also don't understand code.
I can tell "new" people don't write software the way I write software. That is for sure. The level of caring about how well the software works is low, is my impression. And they dont' know how to test.
AI Cargo Cult is a good term to describe pop-sci-tech-fetishists. I wonder if we can call AI programmers "AI Cargo Cult Code Monkeys"
They hide it because C/C++ give you enough power to actually be dangerous. Modern languages are all stuck in the idiot proofing/ encounter a better idiot cycle.
I don't miss messing with pointers, but the hand holding can definitely go too far.
What's even the point of hand-holding in coding?
I grant you, there might be a language built for non-coders that you might want to do that with, but not with people who's job it is.
The hand holding is because of efficiency and security. Programmers who don't know what they are doing when allocating/freeing memory end up with memory leaks that degrade system performance. Programmers who don't know what they are doing with pointers and references can unintentionally write to restricted addresses and brick the system.
So to avoid these problems, control of garbage collection and direct memory access have been taken from the programmer, and handled under the hood for them. It is all about idiot-proofing.
To avoid these problems... write secure code, and preform garbage collection.
cue Hank Hill scream
C++ also results in stuff happening in unknown spots due to the C/CPP run time support needed for it. With C , it is easy to predict when code will run. C++ has things like static initializers whose code runs "I have no idea when".
In general, if you're relying on static initialization to run at a specific time or in a specific order, you've probably done something horribly wrong in your architecture.
That is true.
I just feel like you have less visibility into the asm that's going to come out of the CPP code vs the C code. I guess that's why it's higher level. For the kernel, though, that would be bad for performance and predictability. I think.
"whenever I feel like it"
Oh there is a rulebook somewhere, 1000s of pages long. I saw it in paper. Though that (C++) was not really ever my corner.
C has simplicity.
C++ has object oriented stuff that's worse than other OO programming languages. C succeeds at what it goes out to do. C++ does not. IMO.
I don't know enough to disagree with you, but I will say I appreciate C much more than a lot of others.