From: Ethan Grammatikidis <eekee57@fastmail.fm>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] remote access to audio devices
Date: Sun, 27 Dec 2009 10:07:13 +0000 [thread overview]
Message-ID: <3BC10147-A971-404F-B310-3BB515C62582@fastmail.fm> (raw)
In-Reply-To: <7273328E-A685-4096-80FF-3AE8B6BEE2C2@9srv.net>
On 26 Dec 2009, at 3:39 am, Anthony Sorace wrote:
> On Dec 25, 2009, at 04:57, erik quanstrom wrote:
>
>>> Java sometimes does turn up trumps where C code struggles on
>>> machines
>>> which were recently considered powerful. Other examples would be web
>>
>> what?
>
> from the rest of his post, i gather that the claim isn't that Java
> vs. C code of equivalent
> quality has C lagging, but rather that some application written in
> Java can beat an
> application of vaguely equivalent description written in C. the VNC
> examples given
> say, basically, that the Java app performs better out of the box
> than the C app, but it
> seems to just be about picking better (for that particular case)
> defaults.
>
> i guess my question is really what this observation is intended to
> illustrate.
>
>
Yes, that would be what I meant. Thanks for writing that Anthony,
these things are all pretty clear in my head, but writing them out
clearly is quite hard work.
--
Ethan Grammatikidis
eekee57@fastmail.fm
next prev parent reply other threads:[~2009-12-27 10:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<F7BCB408-74FB-4E3C-BBAF-C52E0C2A15B3@fastmail.fm>
2009-12-25 9:57 ` erik quanstrom
2009-12-25 14:49 ` Jorden Mauro
2010-01-05 12:10 ` Enrico Weigelt
2009-12-26 3:39 ` Anthony Sorace
2009-12-27 10:07 ` Ethan Grammatikidis [this message]
2009-11-26 0:07 [9fans] Scanners Charles Forsyth
2009-11-26 4:55 ` W B Hacker
2009-11-26 6:39 ` [9fans] remote access to audio devices Sam Watkins
2009-11-26 8:59 ` W B Hacker
2009-12-01 20:44 ` Steve Simon
2009-12-01 22:28 ` Ethan Grammatikidis
2009-12-02 0:26 ` Patrick Kelly
2009-12-02 3:00 ` Sam Watkins
2009-12-25 9:50 ` Ethan Grammatikidis
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=3BC10147-A971-404F-B310-3BB515C62582@fastmail.fm \
--to=eekee57@fastmail.fm \
--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).