9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Roswell Grey <orangecalx01@gmail.com>
To: 9fans@9fans.net
Subject: [9fans] Chrome and 9
Date: Sun,  7 Dec 2014 14:35:51 -0500	[thread overview]
Message-ID: <CA+VQh+xA4rfh24+oaMJUGeOJHxzZz06qh-p1W1zJAA_TfsqHgQ@mail.gmail.com> (raw)

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

It's no question that the Chromebook makes a wonderful candidate to
integrate features of 9 into. The thing was practically BUILT for
distributed computing, what with app servers and cloud integration tightly
integrated into the hardware. What I was thinking was creating a chrome
extension for 9P and the distributed file system, so that there'd be an
easy way to connect 9 machines and maybe even create a chrome 9 grid for
super processing. What would be your opinion on doing such a thing?
Practical? Waste of time? Wanna help?

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

             reply	other threads:[~2014-12-07 19:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-07 19:35 Roswell Grey [this message]
2014-12-07 23:59 ` da Tyga
2014-12-08 10:31   ` Sergey Zhilkin

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=CA+VQh+xA4rfh24+oaMJUGeOJHxzZz06qh-p1W1zJAA_TfsqHgQ@mail.gmail.com \
    --to=orangecalx01@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).