I’m saying two game-over vectors is worse than one.
I don't see any viable alternatives to C for robust kernel programming, but Linux doesn't even use C robustly.
-
-
Idiotic things like malloc'ing & refcnting struct cred rather than putting it in task struct directly.
-
There are viable alternatives to C, like Rust without any of the standard libraries above the layer of libcore.
-
Maybe someday, but for now I don't see how a language whose spec isn't even near-stable is usable for kernel..
-
It's not like the C specification is stable... and it only gained a memory model with C11, which is a big deal.
-
Previously POSIX specified a much stronger (more constr) mem model to which all usable compilers had to comply
-
And the pre-C11 [lack of] memory model in C was sufficient for specifying non-concurrent behavior fully.
-
So IMO from a practical standpoint C11 significantly weakened the memory model, rather than adding it.
-
From a practical standpoint, they've had major issues with their own informal model not matching how GCC works.
- 6 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.