edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Chris Brannon <chris@the-brannons.com>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] interprocess messages
Date: Tue, 09 Dec 2014 07:57:30 -0800	[thread overview]
Message-ID: <87h9x4vms5.fsf@the-brannons.com> (raw)
In-Reply-To: <20141109091302.eklhad@comcast.net> (Karl Dahlke's message of "Tue, 09 Dec 2014 09:13:02 -0500")

Karl Dahlke <eklhad@comcast.net> writes:

> and compiling js code into native cpu code for speed.
> Really? A true js compiler?

I'm not sure how familiar you are with Google Docs, but they've
implemented a word processor, spread sheet, and presentation
manager as web apps.  So they definitely have an interest in making all
this stuff fast.  Also, on devices like the ChromeBook, the OS is
basically the browser.  Yeah, it's Linux under the hood, but unless you
replace the software on it, you'll be doing everything through the
browser.

And then there's just plain sillyness, like the x86 emulator implemented
in JS.  Yes, you can actually run Linux in an x86 emulator inside your
browser.  Why you'd want to do that is another question entirely.

Regarding my earlier post about V8, here are some links
describing the issues that Gentoo had with it.

http://comments.gmane.org/gmane.linux.gentoo.devel/88222
http://phajdan-jr.blogspot.com/2013/11/when-libraries-you-use-are-moving-too.html

I'm not at all against the switch, if it will be nicer to deal with.
But if we do switch, we probably want to bundle our own version of V8
with edbrowse.

Getting a V8 hello world is definitely on my to-do list.

-- Chris

  reply	other threads:[~2014-12-09 15:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-09 14:13 Karl Dahlke
2014-12-09 15:57 ` Chris Brannon [this message]
2014-12-09 23:01   ` Adam Thompson
2014-12-09 18:23 ` Adam Thompson
  -- strict thread matches above, loose matches on Subject: below --
2014-12-08 19:27 Karl Dahlke
2014-12-09  7:53 ` Adam Thompson
2014-12-09 11:06 ` Chris Brannon

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=87h9x4vms5.fsf@the-brannons.com \
    --to=chris@the-brannons.com \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    /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).