Gregory's Server@lanodan @MischievousTomato @shebang
> - Lack of things like keyboard accessibility
Yeah, you can tweak this kind of thing; sam is pretty keyboard-friendly out of the box. You can script keyboard events arbitrarily, even, just put a pipe between the keyboard device and rio. I don't because it's not useful but I used to do this kind of thing with Inferno, but I can understand the wrist issues with mice. (Although Thinkpads are nice for this, but lateral stress on my index finger tends to make the joints sore if I use just my laptop for a few days.)
> No multi-monitor support
Don't quote me on this, but I think that's been fixed. I usually use drawterm anyway; there's stuff that lives in Linux that I can't avoid. (Linux is my new Windows.) You can run $n operating systems now that you can get a pile of computers without even having to dumpster-dive and you can run 30 VMs on each of them.
> Move more things out of the kernel, as I think that would make it easier to create and maintain drivers while also getting better stability (haven't ran Plan9 enough to judge that part though)
Yeah, it doesn't work like that; it's trivial to play with drivers, and it's ridiculously stable but it doesn't actually need to be: your files live on the fileserver (which should be stable), you run your stuff on a CPU server and connect to a terminal server and you can reboot basically any of those without consequence, and it's had kexec() since forever (reboot $kernelpath) so as long as you don't write a kernel that crashes the machine and also hoses remote debugging, it's like a few seconds to test a new kernel. So stability's less of an issue, but I've never gotten it to crash by normal means.
But I'm interested in what you want, like analogous to the stuff I was talking about. What do you want your OS to do? Like, one step up from feature bullet points.
> - Lack of things like keyboard accessibility
Yeah, you can tweak this kind of thing; sam is pretty keyboard-friendly out of the box. You can script keyboard events arbitrarily, even, just put a pipe between the keyboard device and rio. I don't because it's not useful but I used to do this kind of thing with Inferno, but I can understand the wrist issues with mice. (Although Thinkpads are nice for this, but lateral stress on my index finger tends to make the joints sore if I use just my laptop for a few days.)
> No multi-monitor support
Don't quote me on this, but I think that's been fixed. I usually use drawterm anyway; there's stuff that lives in Linux that I can't avoid. (Linux is my new Windows.) You can run $n operating systems now that you can get a pile of computers without even having to dumpster-dive and you can run 30 VMs on each of them.
> Move more things out of the kernel, as I think that would make it easier to create and maintain drivers while also getting better stability (haven't ran Plan9 enough to judge that part though)
Yeah, it doesn't work like that; it's trivial to play with drivers, and it's ridiculously stable but it doesn't actually need to be: your files live on the fileserver (which should be stable), you run your stuff on a CPU server and connect to a terminal server and you can reboot basically any of those without consequence, and it's had kexec() since forever (reboot $kernelpath) so as long as you don't write a kernel that crashes the machine and also hoses remote debugging, it's like a few seconds to test a new kernel. So stability's less of an issue, but I've never gotten it to crash by normal means.
But I'm interested in what you want, like analogous to the stuff I was talking about. What do you want your OS to do? Like, one step up from feature bullet points.
(I hate ARM shit though, I want a boot ROM, even if it's a cursed BIOS)
I think it's stuck to not having multimonitor for me because all my GPUs are AMD and I guess it would only support that on Intel ones where it already has more than just VESA.
Thing I wish to be able to do with Plan9 are:
Replace at least most of the terminal/GUI stuff that I have on linux.
I'm tired of things in curses that never speak/listen to other programs and are stuck to a crude interface. Like shit today means I need at least a basic HTML viewer for RSS/Atom, parts of Email, … and while you can emulate a terminal in curses apps to spawn lynx/w3m in them it's a nightmare to actually use since shortcuts conflict between each others in an unpredictable manner. And using --dump is just a hack and it's forever stuck to plain text.
Meanwhile Qt/GTK/… makes me want to throw everything away because one is just proprietary-developed + open-source released, while the other is just happily jamming into a wall everytime the CADT refreshes itself.
And I do wish to move my audio programs to Plan9, I could also move it to a BSD but… I don't really like those systems, they're not as hackable as I want an OS to be.
Pipewire on the linux side of things at least seems to be going in a good enough direction by linux standards but it's not going to beat just simply writing into /dev/audio and easily being able to hack on it with knowing that the rug won't be pulled from under you at some point by the CADT mob making yet another half-baked solution be the de-facto standard.
(I hate ARM shit though, I want a boot ROM, even if it's a cursed BIOS)