From: Skip Tavakkolian <skip.tavakkolian@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 11:16:38 -0700 [thread overview]
Message-ID: <BANLkTins7TqUHJ0JpqJx=VkQdaPWLwW=dA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTikyyv7Hg5oHx=VyQESw4=Kn6LF2cg@mail.gmail.com>
i don't know what compromise you're talking about; anything that can
implement and use 9P is a legitimate component to attach to Plan 9.
browsers are the predominant way that users connect to the Net;
websockets in html5 provide the ability to establish a full duplex tcp
connection. why shouldn't we want to use the browser as a 9P server or
client?
On Tue, May 17, 2011 at 10:23 AM, Peter A. Cejchan <tyapca7@gmail.com> wrote:
> Folks,
> i am very unhappy seeing this kind of discussions here (and, the wasted
> potential to do something more useful in my eyes, sorry, but IMHO)... it
> resembles me very much the times when Steve Jobbs compromised the ideas of
> the NeXTstep, first downgrading it to the OpenStep for Windoze users, then
> downgrading to MacOS X...... look, what happened to linux, bsd, etc: it's
> all approaching the silly model of windoze, you'll kill me but its IMHO... i
> don't want zillion of comp. languages to learn when they are capable of
> mostly the same ... please, please, Bell Labs people, please, do not
> compromise the ideas... believe me, it was not very much easy to me to throw
> away all the boilerplate apps served on linux and do the C port of many
> (>70) of them to switch to native plan9, but i feel it was one of the best
> decisions in my (professional) life, and remember, i am not a programmer, i
> am a paleobiologist, hence , user...
> Just my sad feelings... native plan9 deserves more focus than it gets,
> imho... i would hate to see plan9 as a plugin for Mozilla 20.0
>
> Sincerely, Peter, aka
> ++pac
> a proud user of plan9 since 2001...
>
>
next prev parent reply other threads:[~2011-05-17 18:16 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
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 [this message]
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='BANLkTins7TqUHJ0JpqJx=VkQdaPWLwW=dA@mail.gmail.com' \
--to=skip.tavakkolian@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).