Yes. It's called libC and in many cases is a wrapper around syscalls(). The API is POSIX, but libC is the "C specific API that implements POSIX".
You can say that again...
My problem with Rust is it's obfuscated chain of custody i.e. backdoors in compiler risk.
I have asked someone who has prototyped nontrivial operating systems in Rust....
While this is a possibility, I don't consider governments or their TLA agencies to be smart enough or pervasive enough to pull this off. They can't even do (what's supposed to be) their main damn job right!So, a kind of honey trap, masquerading as a 'more secure' solution; and recommended/mandated by the goobermint and NSA. Nothing would surprise me.
Rust & Memory Safety: What NSA, CISA & White House Say (2026) - Rustify
Governments are mandating memory-safe languages. Here's what the NSA, CISA, and White House reports say about Rust and what it means for your career.rustify.rs
Which reminds me of Ken Thompson's classic paper on compiler security.
We're good on the way. Keyboards are already sofrware-abstracted. You can't do a lot with a USB-keyboard and some wires. Still need PC-standard and a high-level USB driver to read or send something. Phones are ruled out completely. That's a touchscreen layer on 1 specified fake-open kernel. Everhting happens far from the metal.
See, this is what gets me. Who wrote the compiler for Rust?
When I walked into my first and only "agile shop". the model was generic coders taking whatever JIRA ticket the idiot lead decided to assign, expecting that every coder could do any ticket that came thru in the specified amount of time...and then being performance evaluated simply by ticket burndown rates...and lets not forget the "team standards" based code reviewed. based on 30 yo paradigms and which forbid use of any construct that the idiot lead and his golden haired boy didn't understand. The best way to describe that place was "untapped potential" they had good people, but misused them terribly, and those who didn't stroke the "idiot managers" egos left after a few months.
Sounds like <assert.h> to me. Yeah, I'm being facetious. Of course, Rust does have some technical merits, moving that type of constraint validation, from run-time to compile time.
All they need is "warm bodies" who can do "baby steps". Sounds truly terrible. Don't think I could work in a shop like that. Not sure I'd last the week.
I lasted six months. They canned me because I refactored a 2000 line long struct copy module to be about 150 lines, using pointers instead of explicitly referencing every horrendously long nested struct assignment. Of course by this point I was outspoken about my displeasure with the stupidity of technical management.
That deserves a
for staying power, but you gotta do what you gotta do. Ah well, that kind of refactoring would reduce their KLOCs count, which probably means some bean counter thought that they had been less 'productive'... as we say over here, "never mind the quality, feel the width" 
