— Yeah, nothing about the kernel changes how V8 works
But you could also run regular js in the kernel with a scheduling mode which emulates what it expects
— So this will be an additional API layer on top of what node provides?
— It will exist exclusive of node, but you could do that
— I have a stack in mind when I deploy it as a cloud OS, it will be vanilla V8 with an extremely tiny interface to a NodeJS process
— NodeJS process will open the Linux kernel up to the JS kernel, and then the Linux kernel opens up the hardware to the JS kernel
— Cloud OS will be server centric, IE an exokernel paired with a library of server processes
— In multilevel priority queue scheduler mode, those servers are prioritized above userland processes, inching close to real-time response times
— I say close because I don't have that benchmark yet, but I know the CS is sound enough to at least have good context switching speed between a small handful of processes
— Im just lost in kernels.. wat are you talking about man?
— You mean you can speed-up JS code or...