AI isn’t going to magically help solve problems with technology. Frankly I’m tired of technology. I miss people.
2,176 karma · joined April 25, 2011
AI isn’t going to magically help solve problems with technology. Frankly I’m tired of technology. I miss people.
I see no mention of CppNix other than from certain detractors.
Of course there's corporate sponsorships, how else do you expect people to work on this stuff full time and eat. Food and Shelter aren't handed out for free last I checked.
Mind boggling statements.
You don’t show that you can cut wood, you show you can build things with a portfolio of work. Like every other damn profession.
There's a cost to jump from memory protected context (user mode in effect) to supervisor mode, usually an interrupt at minimum. In reality there's typically some syscall mechanism which requires argument marshalling, verification, unmarshalling. Lest you catch a TOCTOU issue.
There's a cost to managing the memory regions... both in wasted memory (page aligned/mpu region aligned) and cpu requirements (reprogramming page tables/mpu regions).
None of that is free of charge and those costs add up quickly.
No need for IPC or syscall marshalling when you can simply do function calls without the hassles of MMU permissioning.
Like why is a microkernel needed today for this sort of thing, if its purely for security of memory then... well there's other ways of solving that problem completely outside of hardware memory protection schemes at this point in my mind.
We're so steadfastly stuck in this mindset of needing memory protection and pointer protection (CHERI) because of the insanity that C and its like bring to the table. Restricting the software to safe rust does much the same job. Memory is protected, lifetimes are protected, and better still data races are protected.
E.g. see rtic-rs and how tasks are written. Without unsafe, no memory is accessible outside what is given explicitly to the task. And checking for unsafe rust can be done in an automated fashion at compile time.
Or maybe I'm totally wrong which is quite possible!
Step 2, actually document the part well enough for third party implementers.
Step 3 don’t threaten to sue everyone and anything that glances at it.
What we really need is C2
C with constexpr, type traits, and generics… oh wait this exists! Rust, Zig, etc
Sadly tool chains for some platforms are proprietary variants of llvm clang and fail to include rustc
If you look at what things like RTIC and embassy are doing I have to say its pretty appealing. Make programming the interrupt state machines a little nicer with async rust, and in RTIC's case without a chance of deadlocks.
That's pretty stellar, and at a footprint and memory usage that is far lower than even the smallest RTOS can muster.
Seems like a pretty easy win for a majority of voters. Militarization shouldn't be the only imho, but some kind of process needs to happen there. People paying coyotes and dying in the river and desert is wrong. People being stuffed in cages and treated poorly is wrong. Letting everyone in unchecked and unfettered is also wrong.
FSF donor listing/sponsorship listing is... spartan at best.
Compare this to Linux Foundation and LLVM Foundation, and generally wide swaths of both corporate and personally interested parties contributing time and money and tell me that trying to be idealistic is good for FOSS. The evidence I see is to the contrary.