9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@labs.coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] crazy idea - drawterm in javascript?
Date: Tue, 17 May 2011 14:18:45 -0400	[thread overview]
Message-ID: <867ebc36addb575545f253fda3ca2026@coraid.com> (raw)
In-Reply-To: <BANLkTinNMQ7H9bjSh8nSqNnfMdj7rFDzXw@mail.gmail.com>

> What the hell? They're not saying, "Screw running on hardware, let's
> just boot the whole system in Javascript under a browser", they want
> to let you connect to your Plan 9 system from a web browser, because
> you can find a Javascript-supporting web browser anywhere (except Plan
> 9) these days.
>
> As fgb would say, relax. No "Bell Labs people" have even commented on
> this thread, and if anybody wants to implement this, it's their own
> damn business. Writing a drawterm replacement in Javascript is not
> going to "downgrade" Plan 9. In fact, it would be rather useful--now
> when you're away from home, you can use somebody else's computer to
> connect to your CPU server and read your mail, for example.

relax, man.  i understand peter's perspective.  and i don't think
it's unreasonable.  just think about how dbus has downgraded linux.

on the other hand, i think a js virtual machine (mips would be nicer
than x86) might be interesting.  drawterm has always been a clever
hack.  it would be nice to have emulated environment that's more
portable than 9vx and not tied to 32-bit x86.

one would then be able to write applications for non-plan 9 users
in plan 9.  clearly they will have a browser.

not that i'm signing up or anything.  :-)

- erik



  reply	other threads:[~2011-05-17 18:18 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-17  7:00 Adrian Tritschler
2011-05-17  7:38 ` erik quanstrom
2011-05-17 15:02   ` Russ Cox
2011-05-17 13:59 ` Eric Van Hensbergen
2011-05-17 17:53   ` Joseph Stewart
2011-05-17 17:57     ` John Floren
2011-05-17 18:04       ` Joseph Stewart
2011-05-17 18:16         ` Jason Dreisbach
2011-05-17 18:00     ` Russ Cox
2011-05-17 15:08 ` Skip Tavakkolian
2011-05-17 17:23   ` Peter A. Cejchan
2011-05-17 17:31     ` John Floren
2011-05-17 18:18       ` erik quanstrom [this message]
2011-05-17 18:46         ` a z
2011-05-17 19:04           ` Skip Tavakkolian
2011-05-17 23:05           ` David Leimbach
2011-05-18  9:15         ` dorin bumbu
2011-05-18  9:40           ` a z
2011-05-17 22:49       ` errno
2011-05-17 23:40         ` Jacob Todd
2011-05-17 23:58           ` errno
2011-05-18  0:18             ` David Leimbach
2011-05-18  1:02               ` errno
2011-05-18  8:33           ` Balwinder S Dheeman
2011-05-18  9:49             ` Peter A. Cejchan
2011-05-18 12:24             ` blstuart
2011-05-18 14:23               ` David Leimbach
2011-05-18 15:37               ` Balwinder S Dheeman
2011-05-18 15:46                 ` erik quanstrom
2011-05-20 12:41                   ` Balwinder S Dheeman
2011-05-19  1:04                 ` blstuart
2011-05-18 15:58               ` ComeauAt9Fans@gmail.com
2011-05-17 18:16     ` Skip Tavakkolian
2011-05-18  6:31     ` Peter A. Cejchan
2011-05-18  7:28       ` Charles Forsyth
2011-05-18  7:30         ` Peter A. Cejchan

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=867ebc36addb575545f253fda3ca2026@coraid.com \
    --to=quanstro@labs.coraid.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).