7 ms·
I was fascinated with Plan 9. It just has really cool ideas in its design. It has been said before and I agree. The problem with Plan 9 adoption isn't Plan 9.
by rdtsc 13y ago
I was fascinated with Plan 9. It just has really cool ideas in its design.
It has been said before and I agree. The problem with Plan 9 adoption isn't Plan 9. Plan 9 is beautiful. The problem is that Linux is quite alright as well.
Also, Linux has drivers for more hardware when Plan 9 was ready to be played with. Plan 9 doesn't. It is a chicken and egg problem. I remember trying Plan 9 and it just didn't have drivers for some of my hardware. It was like Linux in back in the days.
- pjmlp 13y agoPlan9 is fine if you only care about daemons and command line interfaces.
- klrr 13y agoUnix is more command line oriented, honestly. Plan 9's is really GUI centric, although not a ordinary GUI.
- pjmlp 13y agoI have used Plan9 and don't agree, specially looking at the examples of Amiga OS, Atari OS, Mac OS (X), Windows, OS/2, IRIX, NeXTStep, Native Oberon, SmallTalk...
- weland 13y agoHave you also used Acme (non-trivially)? The UI makes heavy use of text (the whole thing being a text processing environment after all) but the graphical aspect is highly significant, and most of the (fairly complex) interaction is via mouse. The Plan 9 userspace excels at tying text-using utils, but the traditional Unix CLI is not the means by which you tie them. Even the terminal is quite far removed from a typical command line.
- pjmlp 13y agoAcme is based on how the whole Native Oberon OS works, which provides a much better UI experience using the same principles, specially the last version (System 3).
- deleted 13y ago[deleted]
- pjmlp 13y agoThat is nothing new, it is how Native Oberon works (1987), which is based on Smaltalk (1972) works. In Native Oberon, every module can export functions as commands that are mouse callable in the UI and take input from mouse selections, which can even be UI objects (gadgets). Most of the mouse/keyboard interactions in Rio were already available in Native Oberon.
- nmcfarl 13y agoWhich is fantastic endorsement. GUIs and the Web may be nice for mucking about - but when I work - I work on the command line (or in emacs). All I truly care about is daemons and command line interfaces. Of course - my daemons and command line interfaces have to produce pretty output, for people who care about other things. But those people are not me. So I installed Plan 9 from User Space[1] last night - largely on this recommendation :) [1] http://swtch.com/plan9port/ http://swtch.com/plan9port/
- pjmlp 13y ago> All I truly care about is daemons and command line interfaces. Welcome to the world of computing in 70's. Some of us prefer the future. :) I enjoy GUIs since my Amiga 500 days.
- qu4z-2 13y agoI feel like GUIs these days cater too much to novice users. Obviously the old-school terminal/no-graphics style is pretty dated, but I have yet to see a nicely integrated solution with the advantages of GUIs and the power of the cli.
- pjmlp 13y agoMaybe, but I don't feel that way. I do enjoy the power of the CLI for automation and pipelining of commands and build scripts. However I am a visual guy and also enjoy the power of IDEs when coding. So I rather use the GUI and make use of the CLI when required, than the other way around. This was exactly how one would use Amiga OS. Spend most of the time in Workbench and use Amiga DOS when required to do so. Or even the old Mac OS, where a terminal was a third party application. There was no command line, only GUI.
- nmcfarl 13y agoSo after your first comment I was wondering what GUI gives you as far as tools in an IDE that you couldn't have with curses style terminal-based interface. Emacs (and vi) do a wide assortment of refactorings, auto-completions, multipaned outputs, large scale cut and pastes etc. I couldn't think of anything that actually needed graphics. Given that i couldn't think of any reason why an IDE needed to be a GUI. That is to say I can see people preferring the look, or the use of a pointing device, but I couldn't figure out any coding features that where actually GUI-only. You have any I couldn't think of?
- sillysaurus2 13y agoWell, the problem with Plan 9 is that it requires everything support the Plan 9 protocol. The entire stack has to speak Plan 9, otherwise nothing works. So anything that interacts with it would have to support the full protocol, whereas Unix is just "pipe this output stream into that input stream," which is quite a lot easier to adopt.
- p9idf 13y agoIt's not unusual for an operating system to require its programs to use its system calls. A Unix program that doesn't speak Unix protocols is just as useless as a Plan 9 program that doesn't speak Plan 9 protocols. It's a moot point though, since you'd have a difficult time unwittingly making a compiler generate a program that doesn't work on its own operating system. Pipes on Plan 9 use the same pipe, read, write, and close system calls as Unix does; they are an equivalent amount of work to use (or adopt, as you say).
- throwaway2048 13y agoits important to note that "speaking the plan9 protocol" amounts to normal file operations like read(), write(), stat() etc. This also works fine with pipes.
- derefr 13y agoI'm amazed that "drivers" are still a consideration in OS design anywhere other than embedded systems. Why aren't we writing our operating systems to target hardware-abstracting hypervisors yet? Isn't that an obvious separation of concerns?
- gizmo686 13y agoIsn't the BIOS supposed to be the hardware abstracting layer we run our programs directly on? That doesn't work any more (because BIOS is a legacy mess), so now we have kernels that act as the hardware abstraction, and write operating systems on top of those. Of course, now you need to target you operating system to a kernel.
- derefr 13y agoYes, the BIOS is exactly what's supposed to be doing the hardware abstraction, such that jobs like "read a block from a block device" are done via hardware interrupts, not system calls. I think hypercalls are a good compromise, these days; what is a hypervisor but a BIOS running on the CPU? There are already specialty OSes that take this tack--things like Openmirage (http://www.openmirage.org/ http://www.openmirage.org/) and Erlang on Xen (http://erlangonxen.org/ http://erlangonxen.org/). It could be done with a general-purpose OS just as easily.
- derleth 13y ago> what is a hypervisor but a BIOS running on the CPU? Generally, a hypervisor implies a VM which multiplexes the hardware and allows multiple OSes to run at once, which is more than any BIOS has ever done. Also, a hypervisor generally doesn't provide any hardware abstraction, to be compatible with existing OSes which expect to be alone on the hardware.
- rjsw 13y agoIf the hypervisor is a paravirtualized one then it will provide hardware abstractions. The Openmirage project described above is essentially an OCaml Machine, it only needs drivers to talk to the generic Xen devices for disk, network, console etc...
- rektide 13y agoThe problem is that Linux is quite alright as well. The advantage of plan9 was "at scale," being able to commingle multiple system's resources in interesting novel ways. This has never been and still is in no ways Linux's strength. Linux is inward focused: a monolithic kernel designed to serve as a pleasant base for anything running under it. There are probably near a thousand different Node.js projects each implementing some kind of coordination layer between Node.js processes (ex: https://github.com/amino/amino https://github.com/amino/amino) and similar efforts abound on for all other applications to be coded against (Hazelcast, Hadoop, &c). Why? It's all done as application framework level because the Linux operating system's design space is sitting on a box and running. The fanciest interconnect you're going to get is when you first modprobe in USB-IP (allows network control of a usb peripheral). It's downhill, and back to writing applications if you want to push on. Linux is definitely quite alright. We're fine with Hadoop, running on the JVM, running on Linux. We were delighted to have a desktop Unix, to have X running- the never ending parade of "year of the linux desktop" stories, year after year. Linux arose when we wanted better ways to run things on a box, and most problems fit on a box. Linux was what we wanted, took care of the pressing matter of running a single box, and it was good at that, whereas when it and Plan9 were in their early days, it was a harsh and hostile landscape and we weren't good at working within the confines of the box. Plan9 has always been for those cases where you abutted the constraints of the box, and wanted to think more openly more broadly about the problems about us- and plan9 was for those who wanted to reap solutions that could scale and reach out in a common interoperable serviceable way. It was ahead of it's time, and we couldn't picture the use of a fabric that would let the boxes work together, in part because boxes were still rapidly individually advancing from the very crude, hard to use machines of the mainframe days into things we could begin to use. Thanks Linux for getting us so far, but I tend towards suspecting that thinking of a running environment that thinks chiefly of itself, that remains firmly about it's own box, is too old world to be of much real service these days.
- rdtsc 13y ago> There are probably near a thousand different Node.js projects each implementing some kind of coordination layer between Node.js processes (ex: https://github.com/amino/amino https://github.com/amino/amino) and similar efforts abound on for all other applications to be coded against (Hazelcast, Hadoop, &c). Why? There is only one Erlang though and it has been around for 20+ years. It has built in distribution and automatic failover. Yes it is built on top of Linux/Mac/Windows OS. But wait, that's not all. There is this project that basically attempts to thin out the OS and replace it with Erlang -- http://erlangonxen.org/ http://erlangonxen.org/ -- Erlang VM implemented on top of Xen hypervisor. To make it even more interesting and bring it back home -- the underlying clustering support is based on 9P (the plan 9 distribution protocol). I think that is pretty cool.
- rbc 13y agoYou can run Plan 9 under Xen, Amazon AWS being one of those places. I've been running it under VirtualBox as well. If you are already using virtualization, the Plan 9 device drivers may be less of an issue.
- RamiK 13y agoQemu(KVM) works as well.