Christmas Comes In July For An Open ATI (Phoronix)
Christmas Comes In July For An Open ATI (Phoronix)
Posted Jul 27, 2008 23:03 UTC (Sun) by nix (subscriber, #2304)In reply to: Christmas Comes In July For An Open ATI (Phoronix) by drag
Parent article: Christmas Comes In July For An Open ATI (Phoronix)
Some people try to stuff a lot of functionality into the kernel: http://savannah.nongnu.org/projects/schemix/ (appears to be dead, perhaps because all the developers went insane).
Posted Jul 28, 2008 9:38 UTC (Mon)
by wingo (guest, #26929)
[Link]
Posted Jul 28, 2008 10:17 UTC (Mon)
by tialaramex (subscriber, #21167)
[Link] (1 responses)
Posted Jul 28, 2008 14:47 UTC (Mon)
by nix (subscriber, #2304)
[Link]
Christmas Comes In July For An Open ATI (Phoronix)
I just want to say that that link is triple awesome.
Christmas Comes In July For An Open ATI (Phoronix)
Actually that is sort-of awesome. If you're going to bolt a language into the kernel then it
only makes sense for it to be Scheme, not only because it short-circuits Greenspun's Tenth
Rule but also because Scheme users won't be disappointed by the kernel's rather sparse
amenities. And even better on a modern kernel you'll run out of stack almost immediately which
makes it exactly like trying to use a real Scheme implementation on old hardware (or in my
case, thousands of them in parallel on 1990s hardware).
Christmas Comes In July For An Open ATI (Phoronix)
Well obviously the sane thing to do is to make the Scheme stack not be implemented in terms of
the C stack.
This makes it easier to implement call-cc as well, and of *course* a kernel imeplementation of
Scheme needs call-cc. :)
(ideally you'd have jailed and non-jailed processes, where the jailed ones have access to no
more than a normal userspace process would except they're implemented by a kernel-space
interpreter. Ideally ideally it'd JIT-compile everything. I'm overthinking this.)