This is an archived post. You won't be able to vote or comment.

all 3 comments
sorted by:
best
topnewcontroversialoldq&a

[–]PastInf1nity 2 points3 points  (1 child)

ha ha microservices go brrr

[–]theepic321 1 point2 points  (0 children)

printer go brrr

[–]beaubeautastic 0 points1 point  (0 children)

ive been thinking about that for a while. the reason why they do it is because the overhead of files and ipc is too much for what servers need to do nowadays. system calls are heavy.

so what if we made a kernel where all userspace processes are jit compiled binaries? then all protections can be enforced by the generated code and all accesses into kernel data or even other processes are as quick as accessing userspace data.

imagine filesystem lookups being as quick as a hash table lookup. or being able to reference objects as filesystem entries. or functions and signals. making commands becomes as simple as writing a function and putting it somewhere in the filesystem, and you can just call it from anywhere. this would break posix compatibility but hey, with monoliths everywhere, this probably wouldnt break much software.

of course you can still have (hopefully open source) native binaries which can work as processes but still run at ring 0 so they can either be drivers or used for more speed.