No shit
slowcakes
joined 1 month ago
That was what he was talking about at the conference, he literally asked for help about how things work, so he could write better APIs that they are more comfortable using.
But the response was we don't want to write rust.
What compromise? Half code should be in rust?
What does this even have to do with rust developers, The language rust gives us the ability to have more compile time checks, and why is that a bad thing. Do you like security issues in your OS because some dev forgot to handle pointers correctly?
There's no solution, they need not only to accept that rust is going to be part of the kernel but also that it's a good thing. Otherwise how do you cooperate efficiently.
And also if they are so big brained, should be easy to learn rust then, I mean I'm pretty small brained and I know rust.
Yes we are going to enable this feature that is going to be irrelevant in the future, because where building an API in the browser to fetch browser History...
Yeah maybe 10 years late...
Dude what are you on about, there is no rust programmer that want to teach fucking rust to anyone who doesn't want learn...
This has nothing to do with C vs Rust, this has to do with security and enabling more people to develop stuff for Linux.
These so called kernel maintainers you see in the conference are only mainting the parts that they use for their filesystem, they are mainting the API, they are paid by companies who have sold support for ext4, xfs or brtfs etc.. . Of course they don't want to make their jobs any harder by learning a new language.
And of course they obfuscate the API with random naming and undocumented usage, because they want to make it hard for anyone else using trying to use the APIs.
If they don't want to be part of the improvement, then go do something else. Yes rust is better than C for this, because guess what - there are still CVEs being made, because it's impossible to catch everything with you eyes.