9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Marshall Conover <marzhall.o@gmail.com>
To: "9fans@9fans.net" <9fans@9fans.net>
Subject: [9fans] Questions on the browser as a platform if plan 9 had gained marketshare
Date: Tue, 20 Sep 2016 16:48:32 +0000	[thread overview]
Message-ID: <CAK0pxsH9HT49dfxc-38CHjj7Bjnge3A9V8UFYzCAaUb+UtNGhg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1311 bytes --]

>  Ken and rob are currently working at google trying to
make sure it stays so - the idea being that if the stupid people that
control the real OS can't be made to learn at least they'll make
themselves an abstract environment that can hide the past and all the
pain, to then work on interesting, more challenging ideas on the
higher level (in the web) without distractions.

So, to make sure I understand correctly, the idea is to leave the actual OS
behind, and have all future development done entirely in the web, with the
browser as an application platform/web services being the OS, and finding a
way to make web services more composable? And this is being actively worked
on by Rob and Ken? I'm tempted to somehow work in the 9front release title
"Why not as a JS library?"

Is there any more information on this? I'd be interested in seeing what a
design like that would be like, and what challenges they're trying to
address. The browser as a platform and the technologies around it seem like
such a kludge after 20-some years of incremental, meandering progress, I'd
think there might be a lot of difficulty trying to base a simple, solid
system on them. Then again, I'm not a web dev, so I could be
misunderstanding what goes on in that domain entirely.

Thanks again!

mars

[-- Attachment #2: Type: text/html, Size: 3818 bytes --]

             reply	other threads:[~2016-09-20 16:48 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-20 16:48 Marshall Conover [this message]
2016-09-20 19:46 ` hiro
  -- strict thread matches above, loose matches on Subject: below --
2016-10-01 20:17 Marshall Conover
2016-10-01 20:21 ` Jules Merit
2016-09-19 22:00 Marshall Conover
2016-09-21  3:11 ` Chris McGee
2016-09-19 12:44 Marshall Conover
2016-09-19 17:25 ` Chris McGee
2016-09-19 20:55 ` Chris McGee
2016-09-20  6:16   ` David Pick
2016-09-20 17:42     ` Chris McGee
2016-09-22 22:49       ` michaelian ennis
2016-09-22 22:53         ` Chris McGee
2016-09-20  7:47   ` hiro
2016-09-20  8:09 ` hiro
2016-09-17 15:19 Marshall Conover
2016-09-17 16:23 ` Chris McGee
2016-09-17 17:04 ` hiro
2016-09-17 18:51   ` Jules Merit
2016-09-19 17:11     ` michaelian ennis
2016-10-01 15:03 ` James A. Robinson
2016-10-01 15:05   ` James A. Robinson

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=CAK0pxsH9HT49dfxc-38CHjj7Bjnge3A9V8UFYzCAaUb+UtNGhg@mail.gmail.com \
    --to=marzhall.o@gmail.com \
    --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).