2 ms·
> Isn't that nice? All the surrounding code that isn't doing bit-banging still interoperates with this just fine, so you can do your bit-banging to talk to a me
by lmm 5y ago
> Isn't that nice? All the surrounding code that isn't doing bit-banging still interoperates with this just fine, so you can do your bit-banging to talk to a memory controller and then... return a freshly allocated chunk of RAM to the rest of the high level code which has whizzy generic types and whatever.
It's fine, but it's such a tiny fraction of what matters when producing a product that I wouldn't base my language choice on how good the language's support for that kind of thing is. I don't know exactly how e.g. Singularity or MirageOS do their bit-banging - for all I know they might even use a little bit of C or Rust to bridge the gap - but that bit-banging is such a miniscule proportion of what's important to an OS implementation (much less to an actual product built on that OS) that it shouldn't move the needle on language choice. I've never seen anyone put a genuine effort into running general-purpose language x on bare-metal hardware y and have it fail - it's always "we've tried nothing and we're all out of ideas".