From: "Bruce Ellis" <bruce.ellis@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Java
Date: Thu, 17 Jan 2008 15:19:05 +1100 [thread overview]
Message-ID: <775b8d190801162019ne5fefefr6d6eef4a3bc225c1@mail.gmail.com> (raw)
In-Reply-To: <f10b360c0c9673111d15abedfda643f3@yourdomain.dom>
i did the java class loader for inferno. it was a pointless
exercise, and i told them. but then i quit. somehow i was
unimpressed by the situation.
brucee
On Jan 17, 2008 2:48 PM, Federico G. Benavento <benavento@gmail.com> wrote:
>
> > On Jan 16, 2008 11:58 PM, Pietro Gagliardi <pietro10@mac.com> wrote:
> >> Does Plan 9 have a native limbo compiler? I tried Inferno once. It
> >> was slow, and Charon didn't have CSS, so pages were as ugly as on
> >> abaco (which is part of what I'm working on: using X11 to compile a
> >> foreign browser).
>
> I have most of the X11 libs ported to Plan 9, so I can compile things like
> xeyes, of course I don't have an Xserver, yet...
>
> I'd built an SDL kdrive X server, but as soon as a client connects it crashes
> I thought it was SDL port's fault, so I built Xvfb which does everything in
> a virtual framebuffer and had the same problem, so it's not SDL's fault.
>
> my guess is that the problem is between X and ape's select/listen/etc.
>
> now, the question is why do I want X, well...
>
> http://www.tip9ug.jp/who/fgb/opera9.jpg
>
> there you have opera and Xvnc under linuxemu and a vncv(1) window
> to display everything. so, yes I have opera on Plan 9 (thanks to cinap)
> but it's kinda overkill.
>
> if anyone wants to help with the debugging , mail me off list
>
> oh, and about limbo on Plan 9, of course that there is a native limbo
> compiler for Plan 9, you'll have to to run your .dis inside limbo,
> but that's not problem at all, because inferno doesn't waste your
> memory.
>
>
> Federico G. Benavento
>
> ---
> /bin/fortune:
> ERROR CREEPOUT HAS BEGUN
>
>
next prev parent reply other threads:[~2008-01-17 4:19 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-16 23:54 Pietro Gagliardi
2008-01-17 0:19 ` Federico G. Benavento
2008-01-17 1:04 ` Yaroslav
2008-01-17 1:58 ` Pietro Gagliardi
2008-01-17 2:00 ` Pietro Gagliardi
2008-01-17 2:05 ` Iruata Souza
2008-01-17 3:48 ` Federico G. Benavento
2008-01-17 4:19 ` Bruce Ellis [this message]
2008-01-17 8:29 ` Charles Forsyth
2008-01-17 9:03 ` Bruce Ellis
2008-01-17 8:34 ` Charles Forsyth
2008-01-17 8:32 ` Robert William Fuller
2008-01-17 17:48 ` Latchesar Ionkov
-- strict thread matches above, loose matches on Subject: below --
2006-02-07 20:21 [9fans] java bituman
2006-02-07 20:36 ` andrey mirtchovski
2006-02-07 20:42 ` uriel
2006-02-07 20:48 ` Skip Tavakkolian
2006-02-07 20:56 ` Skip Tavakkolian
2004-03-02 0:59 [9fans] Java matt
2004-03-02 13:46 ` Michael Jeffrey
2003-04-16 12:55 [9fans] java peter a. cejchan
2003-04-11 1:16 okamoto
2003-04-11 8:12 ` Fco.J.Ballesteros
2003-04-11 9:04 ` Bruce Ellis
2003-04-11 9:08 ` will551
2003-04-10 5:19 peter a. cejchan
2003-04-10 14:58 ` ron minnich
2003-04-10 15:24 ` David Butler
2003-04-11 5:44 ` C H Forsyth
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=775b8d190801162019ne5fefefr6d6eef4a3bc225c1@mail.gmail.com \
--to=bruce.ellis@gmail.com \
--cc=9fans@cse.psu.edu \
/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).