Social 📸 Photography

faraiweSome folks think I am some sort of <a href="https://beige.party/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> worship fiend.Nothing further from the truth; I simply admire that, in an age of near absolute <a href="https://beige.party/tags/enshittification" class="mention hashtag" rel="nofollow noopener" target="_blank">#enshittification</a> of most commercial software, the whole <a href="https://beige.party/tags/FOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FOSS</a> thing seems to prove itself, time and time again, as a process (community created, refined and supported) that generates Things That Work. Because their objective IS to make it work, not generate "value for shareholders" and help CEOs buy their fifth yacht.I have oodles and buckets of things to pick at, regarding Linux. Monolithic kernel?? Really?? What is this, 1960s? You manage memory HOW? Oh. The list goes on and on, don't get me started. I was a serious enthusiast of the myriad of alternative OSes, in the Cambrian-like explosion of diversity of the 90s. So much diverse, curious, ingenious, brilliant solutions and notions! <a href="https://beige.party/tags/BeOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#BeOS</a>, <a href="https://beige.party/tags/OS2" class="mention hashtag" rel="nofollow noopener" target="_blank">#OS2</a> <a href="https://beige.party/tags/QNX" class="mention hashtag" rel="nofollow noopener" target="_blank">#QNX</a> (ok, 1980s), <a href="https://beige.party/tags/Plan9OS" class="mention hashtag" rel="nofollow noopener" target="_blank">#Plan9OS</a>, <a href="https://beige.party/tags/ReactOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#ReactOS</a>, to name a few out of so, so many other great Alt OSs of the time...Compared to those, Linux seemed to actually freeze and stall evolution, sticking to the limitations of the vision by Torvalds (sorry, man, it's true, plenty of admiration for the guy, but dropped the ball on that kernel) at the time of its inception.However, being the mainstay of FOSS, I use it, champion it, and defend it against ANYTHING commercial.Until someone truly resurrects BeOS (eeeeh <a href="https://beige.party/tags/Haiku" class="mention hashtag" rel="nofollow noopener" target="_blank">#Haiku</a> ... eh....) lolThere./rant

Doc Edward Morbius ⭕<a href="https://merveilles.town/@jbauer" class="u-url mention" rel="nofollow noopener" target="_blank">@jbauer</a> Aside from Minux, which others have mentioned, <a href="https://toot.cat/tags/Plan9OS" class="mention hashtag" rel="nofollow noopener" target="_blank">#Plan9OS</a> implements ... parts ... of this.Several of Jon's comments are contradictory. Among the reasons that a modern Linus system has a huge number of processes is because individual kernel threads and services are exposed as virtual processes. That starts off with at least a thread or several per CPU pipeline AFAIU (it's been a while since I looked into this), plus filesystem journaling processes, and a number of others.If you limit both IPC and filesystem access, you're both hugely limiting and complexifying application interactions. For better or worse, pipelines and disk storage are a maximally-consistent form of IPC. That doesn't mean applications should have unlimited access, but in some cases (e.g., the shell, system processes), any limitations quickly become hugely problematic.I agree that the complexity can be overwhelming, and miss much of the old days myself.

Doc Edward Morbius ⭕<a href="https://floss.social/@Valenoern" class="u-url mention" rel="nofollow noopener" target="_blank">@Valenoern</a> This is the essential idea behind "docfs", which would be a document-oriented filesystem. Its networked sibling being "webfs"."Document" here is in the sense of <a href="https://toot.cat/tags/PaulOtlet" class="mention hashtag" rel="nofollow noopener" target="_blank">#PaulOtlet</a>, of any durable record. That might be a text, image, sound, video, multimedia content, data, software, or an amalgamation or melange.One of my key ideas is that the metadata for these documents would be part of the filesystem, extending the notion of what constitutes file-centric data. I'd like to see some form of bibliographic data presented, where available for public and published media (book, articles, audio recordings, films).Search is another element, and one idea for the filesystem would be as a virtual filesystem in which attributes could be supplied until a single item matching those criteria was found. "Identity is search".For projects, some concept of structured workflows, with groups, tasks, milestones, and contributing data. For a sufficiently structured organisation, security and access controls.I'd like the whole concept to be as commercialisation-hostile as possible, with both copyrights and payments entirely out of scope.<a href="https://toot.cat/tags/docfs" class="mention hashtag" rel="nofollow noopener" target="_blank">#docfs</a> <a href="https://toot.cat/tags/webfs" class="mention hashtag" rel="nofollow noopener" target="_blank">#webfs</a> <a href="https://toot.cat/tags/kfc" class="mention hashtag" rel="nofollow noopener" target="_blank">#kfc</a> <a href="https://toot.cat/tags/maundenaum" class="mention hashtag" rel="nofollow noopener" target="_blank">#maundenaum</a> <a href="https://toot.cat/tags/DublinCore" class="mention hashtag" rel="nofollow noopener" target="_blank">#DublinCore</a> <a href="https://toot.cat/tags/metadata" class="mention hashtag" rel="nofollow noopener" target="_blank">#metadata</a> <a href="https://toot.cat/tags/bibliography" class="mention hashtag" rel="nofollow noopener" target="_blank">#bibliography</a> <a href="https://toot.cat/tags/Plan9OS" class="mention hashtag" rel="nofollow noopener" target="_blank">#Plan9OS</a> <a href="https://toot.cat/tags/Schopenhauer" class="mention hashtag" rel="nofollow noopener" target="_blank">#Schopenhauer</a>

Recent searches

Search options

Administered by:

Server stats:

#plan9os