wow another KHV switched operating systems, I'm impressed.
frequently questioned answers <http://fqa.9front.org/dash1.nothinkpad.pdf>
0.1.3 − Plan 9 is not for you
Let’s be perfectly honest. Many features that today's "computer experts" consider to be essential to computing (javascript, CSS, HTML5, etc.) either did not exist when Plan 9 was abandoned, or were purposely left out of the operating system. You might find this to be an unacceptable obstacle to adopting Plan 9 into your daily workflow. If you cannot imagine a use for a computer that does not involve a web browser, Plan 9 may not be for you.
See: http://harmful.cat-v.org/software/
９ＦＲＯＮＴ ＰＬＡＮ９－ＨＡＴＥＲＳ ＲＥＬＥＡＳＥＤ
9FRONT PLAN9-HATERS RELEASED
*.386.iso 386 pc (more drivers)
*.amd64.iso amd64 pc (less drivers)
*.pi.img arm paspberry pi 1, 2 and 3
*.pi3.img arm64 raspberry pi 3 and 4
I'm looking for a quiet cabin to make me a solemn man. Most visitors only hope to make a joy ride of the bed, but of course they bring company and don't stay long. What might happen to a man who comes alone and stays a while? Could this be the place I've been looking for? Certainly the lack of those sinister web browsers who tempt me so would help. The light creaking of the hinges as the door opens are overwhelmed by the scraping along the base.
It's clear this cabin hasn't had any serious occupants in sometime. The emaciated bookshelf is covered in dust while the bed remains disheveled, and carved slurs decorate the walls. Despite this, a book, the TeX manual, reassures me the plausibility of the task ahead me. I begin taking inventory. I notice several Scheme implementations, none reflecting the hope that gleamed from my eyes, but perhaps they would suffice. More shocking was what was missing, there seemed to be no Common Lisp implementation, nor any version of GNU Emacs, not to mention the many PDF utilities I became accustom to in recent years. Perhaps I could live like this, adapt to my environment, as my father used to instruct me.
I climbed into the dingy disgusting bed to go to sleep. It was only in this moment that I realized what had been in the room all along. It was not-libredjvu, and he had a knife. I panicked, how could he have found me all the way out here, I hadn't seen him in years and he shows up just as I leave society! My hands begin to shake. "Get yourself together!" I think, perhaps I can port libredjvu, or rather r-rewrite those parts of it I need from the standard, and escape with my life. I began to move my hand, and... *curtains close*
( a not entirely shit tutorial: https://pspodcasting.net/dan/blog/2019/plan9_desktop.html )
I cannot actually imagine using plan9 as a desktop. Even something like openbsd is bothersome enough.
>>9
I hate system administration, and dislike mice. Plan9's intelligibility is what tempts me to undertake this project. That I don't use much software, and that what I do use doesn't satisfy also repels me from what I currently have. It'd likely be healthier to simply begin work on what I want, even if it's going to take years.
Why do some people like Plan9? Is there anything fundamentally wrong about UNIX?
>>11
Plan9 has a consistent mental illness. It's still mentally ill, but it has a character you can get to know, it's something you can work with. Perhaps you even find its deviation from sanity charming in a way. The dominant operating systems are erratically mentally ill, their primary redeeming quality being that they exist.
>>11
The OS model is interesting. It takes lessons learned from Unix and the result is an OS that's very well suited for today's networked computer systems. Any networked resource is "available as a file". This is one major feature that results in a "cleaner" system as this very fundamental feature means the individual applications don't need to implement that specific aspect.
>>13
I never really got the "everything is a file" approach. Is making everything a bunch of bytes (or a stream of bytes) really that useful?
>>14
In the case of Plan9 it's used for network transparent IPC through 9p. It makes more sense when you don't have a single address space, but even then it's useful to have a common namespace convention. I've not thought about it much but I'd be interested in finding such a convention which uses tagging rather than heirarchy, but it seems this usually gets ugly.
>>15
Ah, maybe content-based addressing, and narrowing the full address to something readable in buffer when editing. Tagging would then just be used for human interaction.
>>14
For me "everything is a file" usually means "everything is in the file system" more than just "everything is a stream of bytes".