4 ms·
A lot depends on how "systems software" is defined. Very few people have much use for a whole new kernel. Even little pieces of new kernel code are less usefu
by notacoward 12y ago
A lot depends on how "systems software" is defined. Very few people have much use for a whole new kernel. Even little pieces of new kernel code are less useful than before, as various functions (e.g. storage) can be handled just as well in user space. So if "systems" == "kernel" then relevance really has been declining. On the other hand, if one considers "system" to include user-space storage and networking, distributed consensus and service discovery, package and system management, JIT and GC in language runtimes, etc. etc. etc. then we're actually in a bit of a renaissance.
The fact is that kernel/user hasn't been a very interesting boundary for a long time. There are hundreds of systems-programming problems that can be solved on either side of that boundary, except that if you try to solve them in the kernel debugging will be harder and you'll get embroiled in the constant turf wars that are the hallmark of a declining specialty. The idea that only kernel hackers do systems programming needs to die.
- jdimov 12y agoDoes this mean we probably need a new, more minimalistic concept for a modern kernel?
- notacoward 12y agoWe've been moving that way for quite some time, despite Linus's historic dismissal of microkernel ideas. Granular capabilities, FUSE, namespaces, cgroups, containers etc. all take us in that direction. Over the next several years, I think even the kernel grognards will start to see that the "center of gravity" for systems software has shifted to better languages and tools than are available in their sandbox.
- steveklabnik 12y agoThere's been plenty of designs which are minimalistic, but haven't caught on for a variety of other reasons. See exokernels, for example. They're basically the minimum possible kernel.
- noelwelsh 12y agoThis is exactly right. The OS isn't a very interesting system any more. Unfortunately the author still identifies it as the system of interest. For example: > A quote that still holds true, "There has been much talk about component architectures but only one true success: Unix pipes. It should be possible to build interactive and distributed applications from piece parts." This is completely false. REST/JSON has been fantastically successful. There is a huge amount of relevant systems work going on, and distributed systems research in particular has never been more relevant. Major systems today (Cassandra, HDFS, Riak, etc.) are directly informed by research. It's just that no-one is really interested in ttys and pipes anymore, and that's what the author identifies as systems.
- javajosh 12y ago>This is completely false. REST/JSON has been fantastically successful. I am a little unclear as to how REST/JSON competes with Unix pipes. Can you clarify your thinking here?
- noelwelsh 12y agoIt's not competition. It's just that the components people wire together aren't command line processes but web services, and JSON/REST is the de facto standard. The author is still concerned with OS processes when the field of interest has moved on to distributed systems.
- deleted 12y ago[deleted]
- mapcars 12y agoPlan9 is more into distributed systems than everything written with json/rest.
- emmelaich 12y agoThe distributed system of the fairly near future is json/yaml over websockets/http2/spdy. All accessible from the command line or other. 9fans will bemoan the bloat but it will work (mostly :-) and will be popular.