A lot has been said about how Plan9 is "Unix with all the design issues fixed", but as much as I like the idea of "everything is really, really a file", I'm not sure whether I could get used to the Xerox Star style GUI (which you can't easily replace, since it too is exposed to the filesystem), or trade my lovely Vim in for Acme.
And as any actual Plan9 user will tell you while it isn't "Unix with all the design issues fixed", the model of a per process namespace and synthetic files all over the place makes for a very practical and problem solving system.
Many feel the GUI is a joy but you're not forced to use it, there is even a text mode install. (though only use it if you have to :)
GUI (which you can't easily replace, since it too is exposed to the
filesystem)
What? The graphics system is quite nice, there's no reason to replace
that. I'm pretty sure there is nothing tying the graphics protocol to
their GUI paradigm. I think it would be entirely possible to implement,
say, GTK over it.
Vim
There's no reason it couldn't be ported. I would use it if you made it.
It would be nice to have a libdraw based vi, even just in plan9port.
6 comments
[ 3.6 ms ] story [ 26.7 ms ] threadThere is also http://swtch.com/plan9port Plan9 in Userspace
and http://swtch.com/9vx/ which runs the Plan9 kernel in a VM
though dev is currently on an other branch http://9fans.net/archive/2010/10/14
Many feel the GUI is a joy but you're not forced to use it, there is even a text mode install. (though only use it if you have to :)
What? The graphics system is quite nice, there's no reason to replace that. I'm pretty sure there is nothing tying the graphics protocol to their GUI paradigm. I think it would be entirely possible to implement, say, GTK over it.
Vim
There's no reason it couldn't be ported. I would use it if you made it. It would be nice to have a libdraw based vi, even just in plan9port.
There are several parts, links are on the bottom of each chapter.