9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: sirjofri <sirjofri+ml-9fans@sirjofri.de>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] the practicality of plan 9
Date: Thu, 3 Nov 2022 20:35:04 +0100 (GMT+01:00)	[thread overview]
Message-ID: <8731a27e-6579-447b-98ec-d15bf6759fcc@sirjofri.de> (raw)
In-Reply-To: <CANF_3RgSiR7o6NLd8GFLO8K_iVYKC6Ake-Kc59cFwKnTr+kCRA@mail.gmail.com>

Hello,

just wanted to add that (independent of grids) what's especially great on Plan 9 is the general concept of "resource abstraction".

Let's first consider what "resource" means in this context, since it can be anything: computing resources might be the obvious, but user files are also resources, as well as practical abstracted resources from more complex systems and processes. Basically anything can be a resource.

On Plan 9, all of these resources can be abstracted as a filesystem, which is the common abstraction for all things. Those filesystems are of course network ready and there's no type of "special" filesystem unlike on many other operating systems (for example, on linux you have some special filesystem that manages disk space and that embeds into the OS. On Plan 9 it doesn't matter what's under the hood, as long as it talks 9p it's fine).

And since you have fully dynamic namespaces per process basically you can control which exact services (as a filesystem) you want to use for your specific purpose. You want to use a different network card for your process? Just import the filesystem. You want to access another microscope, telescope or camera for your image processing software? Just import that filesystem. That's not a camera but stored images you captured earlier? Who cares. As long as your software doesn't care, just use it.

This also works great with interfaces to hardware or software resources. As long as the interface looks the same you can easily exchange a filesystem with another. Just build your namespace and do what you want.

And since Plan 9 is fully network ready nobody cares about if the filesystem is actually stored on the same machine, a remote machine on the same network, at the other end of the world, or just a small arduino that talks 9p over some weird infrared signal line some teenager constructed in their basement. It just doesn't matter, the system doesn't care.

In my opinion that's where Plan 9 really shines and empowers me to do crazy stuff. Of course it's more ideological and philosophical, but it's a great perspective to have. And it's more fun to work with it that way.

This is also why I think Plan 9 is very modern. There are many new ideas nowadays that you can find within Plan 9 already in a much more elegant way. Take alone the plumber, which is an incredible utility. It's simple and you can find more "modern" (i.e. complex) solutions on android/ios, windows 10+, mac and modern linux environments, but plumber is just more simple and powerful. And that's just one example, pretty sure you cam find other examples yourself.

Well, again I just want to add a small little detail that's great but I write a long passage. Sorry for the long message.

sirjofri

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Td6c4be6d8502dbd0-Mc4800112cc3288d8076ebe16
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

  reply	other threads:[~2022-11-03 19:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-30 17:04 fig
2022-10-30 17:41 ` sirjofri
2022-10-30 18:06 ` [9fans] " adventuresin9
2022-10-30 18:24 ` [9fans] " ori
2022-11-03 17:03   ` fig
2022-11-03 19:35     ` sirjofri [this message]
2022-11-08 23:07       ` fig
2022-11-09  3:20         ` Lucio De Re
2022-11-09  3:50           ` adventuresin9
2022-11-09 23:14             ` fig
2022-11-10  3:55               ` adventuresin9
2022-11-10  4:52                 ` fig
2022-11-10 12:05                   ` hiro
2022-12-18  1:30 ` Ethan Azariah
2022-12-18 16:29   ` cinap_lenrek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8731a27e-6579-447b-98ec-d15bf6759fcc@sirjofri.de \
    --to=sirjofri+ml-9fans@sirjofri.de \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).