From: David Leimbach <leimy2k@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] crazy idea - drawterm in javascript?
Date: Tue, 17 May 2011 17:18:48 -0700 [thread overview]
Message-ID: <BANLkTi=cJZrMcPOOpamHt+HtaHVHSeEWxQ@mail.gmail.com> (raw)
In-Reply-To: <201105171658.09729.errno@cox.net>
[-- Attachment #1: Type: text/plain, Size: 1715 bytes --]
On Tue, May 17, 2011 at 4:58 PM, errno <errno@cox.net> wrote:
> On Tuesday, May 17, 2011 04:40:50 PM Jacob Todd wrote:
> > Writing/porting web stuff to plan 9 will be hard. Writing
> > something that accesses plan 9 from the web will be less
> > hard.
> >
>
> Correct; but also somewhat ancillary to the general areas
> of concern:
>
> > Is it really all that often when a Plan 9 user is in the precarious
> > situation of needing to access his plan9 system from some
> > other person's/party's pc or laptop?
>
Instead of a "traditional web server platform" for web applications this
could be an alternative deployment target.
Use a grid of Plan 9 machines with a "native" interface in JavaScript.
JavaScript front end to a distributed Go application on Plan 9 sounds like a
potentially useful medium to work in.
>
> > Ok, who slipped me the Cr@zy Pills? Just a couple weeks ago,
> > javascript and web technologies were THE DEVIL INCARNATE...
>
> > I realize I'm being unimaginative, but I'm having a very difficult
> > time conceiving what sort of plan 9 application could possibly
> > be appealing to non-plan 9 users.
>
The one that doesn't look like a Plan 9 application, but instead looks like
a useful application?
I don't think Linux was appealing to very many people before it was obvious
one could host a cheap http server on it either.
>
> > The web is the key.
>
>
That's part of it likely, but I think we have to be able to imagine how Plan
9 makes something easier for someone with a web browser. Technology in
search of a use is almost always the wrong way to go, but I think it did
work out in Linux's case.
Dave
> Cheers
>
>
>
[-- Attachment #2: Type: text/html, Size: 2793 bytes --]
next prev parent reply other threads:[~2011-05-18 0: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
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 [this message]
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='BANLkTi=cJZrMcPOOpamHt+HtaHVHSeEWxQ@mail.gmail.com' \
--to=leimy2k@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).