You are not fighting the C++ compiler or showing why the C++ compiler might be annyoing. You are introducing a bug by poorly using a library (which has nothing to do with writing and compiling C++). Ergonomics I believe are fine?
I'm struggling hard trying to understand what or if your comment has anything to do with GP's comment. Perhaps you wanted to tell that the Rust compiler might have stopped you from producing a buggy program, but again, it has nothing to do with GP's comment.
What I see when producing code with AI (C/C++, Qt) is that often it gives output for different versions of a given library. It's like it can't understand (or doesn't know) that a given function is now obsolete and needs to use another method. Sometimes it can be corrected.
I think there will be a point in which humans will no longer be motivated to produce enough material for the AI to update. Like, why would I write/shot a tutorial or ask/answer a question in a forum if people are now going directly to ask to some AI?
And since AI is being fed with human knowledge at the moment, I think the quantity of good material out there (that was used so far for training) is going to slow down. So the AI will need to wait for some repos to be populated/updated to understand the changes. Or it will have to read the new documentation (if any), or understand the changes from code (if any).
All this if it wasn't the AI to introduce the changes itself.
Sorry to ask, but couldn't it be solved with cargo? I hear all the time about the benefits of Rust tooling and zero-cost abstractions.
Why can't a driver just pull/include the latest-dma-bindings crate and glue the gap with zero-cost abstractions?
If kernel DMA code/API changes, then nothing breaks in the kernel (hopefully) and the "Rust devs will quickly solve the changes" theory can be really proven and tested by quickly updating the bindings AND the updating the drivers.
"People should be advocating for their own values and morals. To be an ethical person is to understand your values and do the work to apply them in your everyday life."
Pablo Escobar could say that he understand his values (whatever they were; maybe money and power over all other values?) and that he works to apply them every day. He advocated for his own values and morals (ruthlessly). This doesn't make him an Ethical person.
I did ctrl+f searching for "opinion", "I believe", "I think", etc. I can't find any reference to "opinions".
I read the post as the author decribing facts and imparting instructions of what we should do ("It's time to do X", "The cargo cult metaphor should be avoided") because they believe their knowledge/opinions/morals/beliefs are better than mine, and somehow they can dictate what to do; how should I feel, what should I think.
Otherwise I am oppressing, contributing to oppress, perpetuating something, [insert other accusations].
As in the past 15 years. It's enough already.
The real question is why the author is doing this? Is it ego? Money? Clicks? Pure and true altruism?
And here "virtue signalling" comes as a possible valid answer too.
On the other side, being told what is "bad", what is "good", "right" and wrong", what is "dark" and what is "bright", what I should do and think and why I don't have such good morals, in the past 15 years, was so exhausting...
> Seems archaic today ... run in mere kilobytes of RAM
There is an entire industry that does pretty much that... today. They might run in flash instead of RAM, but still, a few kilobytes.
Probably there are more embedded devices out there than PCs. PIC, AVR, MSP, ARM, custom archs. There might be one of those right now under your hand, in that thing you use to move the cursor.
No one can deny that kernel devs have a valid complain and concerns. Of course Rust and Linux can work together and is feasible, on paper, and everybody wants to see it in the mainline someday.
But in reality working for and with the kernel is more than just writing code. And being realistic, you wouldn't base months worth of work on the hands and the will of some coder that may or may not have your interests in mind that week. Would you?
I have 1 one year old boy and I often think about how should I behave. While the Santa issue is trivial to me, I decided I will lie, or hide the truth for that matter, about some topics to protect his innocence until he's mature enough to understand.
> your kids will know that there are things you will lie to them about
And that's part of growing up. I now know that the dog I barely remember (when I was almost 3 years old) didn't "went with his mom that came to pick him up one day", and understanding why they lied is part of growing up. Instead of triggering a loss of trust now I can say "I see what you did there, now I understand".
Because it is. And is a statement I agree 100% being a +20-years C developer with a hardwired C parser in my brain: Rust, Zig and some (most?) newer C++ syntax is contorted at minimum (to my eyes).
I wish the only difference were about just new operators, but just the fact that the type has to come after the variable declaration is awful to me (also for returning types in functions declarations). One can tell me 100 reasons why Rust does it this way and they'll probably be all true and right, and you can call me all sort of things but this kind of new syntax puts me off right away.
Maybe my morning coffee didn't kick in yet, but where are the lies? Or why dismiss them as lies and then go on a "I've succeeded (or think I had) and this is what I think" monologue?