9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Ori Bernstein <ori@eigenstate.org>
To: 9front@9front.org
Cc: Jacob Moody <moody@posixcafe.org>
Subject: Re: [9front] Enabling a service
Date: Tue, 7 May 2024 23:41:09 -0400	[thread overview]
Message-ID: <20240507234109.5e46e5abaf50a6f0df261047@eigenstate.org> (raw)
In-Reply-To: <102b2835-4207-4f8c-9f29-9da8b459dc2e@posixcafe.org>

On Tue, 7 May 2024 20:05:21 -0500, Jacob Moody <moody@posixcafe.org> wrote:

> > pick this apart, but this is me telling you what worked and didn't
> > work for me, and i'm happy to answer questions in detail.
> 
> I want to expand this with some of my experiences. I tend to run a
> filesystem on the laptop and just sync file between the FS at home
> and the laptop at regular intervals (typically before I travel) but
> I am home more times than not so my experience is a bit different.
> I tend to keep any code of interest checked in to shithub, that way
> its impossible to be caught without access to what I need. I sync the
> .git and go about my day.
> 

I tend to hack from coffee shops quite often, and don't
sync, but will instead pull things into my namespace,
pop up subrios on my home cpu server, etc.

Contrary to many people's experience, I actually find
that for the kind of latency I get over coffee shop wifi
to my home, remote rio sessions behave fairly well (though
displaying static images is quite painful).

> > 
> >> trying to preserve the labs experience
> > 
> > personally, i don't care at all about preserving the labs experience.
> > we already dumped fossil, made tons of changes.  but before you start
> > proposing all sorts of changes to the system it's important to
> > understand exactly what you're changing.  plan 9 was not designed by
> > idiots, or by accident.  everything that went in is the way it is for
> > a reason.  you may disagree with the reason, but it's important to
> > understand that reason before blowing it off.  and yes, people
> > involved with 9front will challenge you on every little detail,
> > because the details are important, and that's why we're all here.
> > 
> > this isn't linux.
> 
> Laptops are generally outside of the purview of what the labs intended,
> computing has gone in interesting directions. However this is not much of
> hurdle really, people lug around operating systems that would really prefer
> to think of themselves as giant computers running in a dedicated room
> servicing a dozen teletypes. Linux has put a lot of makeup on this pig,
> but you can not change its core design principles. Linux folks make do
> with little hacks here and there to improve the experience, you can likewise
> find whatever fits your fancy for how you'd like to reconcile the world of
> modern computing on to a 9front system. We've gained a fair bit of modern
> conveniences (git), the world is your oyster.
> 
> In general though sl here is right, before we ship something with the system
> we will want to make sure things make sense. We don't shove things in just because
> they can be or because someone has expectations that are not met.

There is an open question about how mobile computers
should fit into a Plan 9; so far, I don't have a good
answer.

I don't think turning every plan 9 machine into an
island is the answer.

-- 
    Ori Bernstein

  parent reply	other threads:[~2024-05-08  3:44 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-06 11:32 Rocky Hotas
2024-05-06 11:58 ` Alex Musolino
2024-05-06 12:43 ` ori
2024-05-06 15:16   ` Scott Flowers
2024-05-06 15:37     ` sirjofri
2024-05-06 16:32     ` Stanley Lieber
2024-05-06 22:18   ` Rocky Hotas
2024-05-06 22:59     ` ori
2024-05-06 23:00     ` ori
2024-05-07  8:22       ` Rocky Hotas
2024-05-07  8:29         ` Frank D. Engel, Jr.
2024-05-07  9:03           ` Rocky Hotas
2024-05-07  9:14         ` sirjofri
2024-05-07 21:11           ` Shawn Rutledge
2024-05-07 21:35             ` Kurt H Maier
2024-05-07 21:45               ` sirjofri
2024-05-07 21:54             ` sl
2024-05-07 21:58               ` sl
2024-05-07 23:15                 ` Lennart Jablonka
2024-05-07 23:16                 ` Shawn Rutledge
2024-05-07 23:45                   ` Shawn Rutledge
2024-05-08  0:34                   ` Kurt H Maier
2024-05-08  0:35                   ` sl
2024-05-08  1:05                     ` Jacob Moody
2024-05-08  1:24                       ` sl
2024-05-08  7:22                         ` hiro
2024-05-08 14:04                           ` Stanley Lieber
2024-05-08 12:08                         ` Stuart Morrow
2024-05-08 16:37                           ` Brian Stuart
2024-05-08 20:16                             ` hiro
2024-05-08 21:26                               ` Stuart Morrow
2024-05-08 21:17                             ` Disconnection-tolerant / distributed filesystems (was Re: [9front] Enabling a service) Shawn Rutledge
2024-05-08 14:25                         ` [9front] Enabling a service Jacob Moody
2024-05-08  3:41                       ` Ori Bernstein [this message]
2024-05-08  4:09                         ` sl
2024-05-08  8:39                           ` Frank D. Engel, Jr.
2024-05-08 14:17                             ` Jacob Moody
2024-05-08 15:49                               ` Frank D. Engel, Jr.
2024-05-08 16:10                                 ` Jacob Moody
2024-05-08 16:33                                   ` Frank D. Engel, Jr.
2024-05-08 17:27                                     ` Jacob Moody
2024-05-08 18:00                                       ` Steve Simon
2024-05-08 19:46                                         ` hiro
2024-05-08 19:46                                   ` Roberto E. Vargas Caballero
2024-05-08 20:34                                     ` tlaronde
2024-05-08 14:57                   ` Lucas Francesco
2024-05-08 15:10                     ` an2qzavok
2024-05-08  2:11             ` Thaddeus Woskowiak

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=20240507234109.5e46e5abaf50a6f0df261047@eigenstate.org \
    --to=ori@eigenstate.org \
    --cc=9front@9front.org \
    --cc=moody@posixcafe.org \
    /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).