caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Brandon J. Van Every" <vanevery@indiegamedesign.com>
To: <caml-list@inria.fr>
Subject: RE: [Caml-list] OpenGL
Date: Sun, 11 Apr 2004 02:23:01 -0700	[thread overview]
Message-ID: <OOEALCJCKEBJBIJHCNJDOENGHAAB.vanevery@indiegamedesign.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0404110037090.25700-100000@localhost.localdomain>

Brian Hurt wrote:
> Brandon Van Every wrote:
> >
> > If you want to save time, I will tell you the obvious:
> > Java3D sucked,
>
> What about it sucked, was what I was trying to elicit. [...]
>
> Hmm.  Just found out that Sun recently laid off the last two
> programmers working on Java3D:

Given those results, I think a better question is if there's a
successful 3D API for a GC language out there somewhere.  By
'successful' I mean people have done some large stuff with it, not just
getting to the "hey guys I've got a wrapper" stage.  This I don't know.
All the 3D engines that have made real progress and are commercially
viable seem to be C++, but possibly I have restricted my attention,
having found Nebula.  In any event, 3D graphics guys are overwhelmingly
C++ performance tweakers.

> > but I've never seen hard numbers.
>
> That means you haven't looked.
>
> I follow the benchmarks, which is why I phrased things the way I
> did.  Graphics performance is primarily driven by the graphics card.

I am surprised then that you said you hadn't seen hard numbers.  Those
benchmarks are hard numbers.


Cheers,                         www.indiegamedesign.com
Brandon Van Every               Seattle, WA

20% of the world is real.
80% is gobbledygook we make up inside our own heads.



---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.643 / Virus Database: 411 - Release Date: 3/25/2004

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


  parent reply	other threads:[~2004-04-11  9:16 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-08 15:11 Jon Harrop
2004-04-07 16:07 ` Issac Trotts
2004-04-08 16:35   ` Jon Harrop
2004-04-08 20:19     ` Issac Trotts
2004-04-08 20:46       ` [Caml-list] Re: Triangle (was: OpenGL) Christophe TROESTLER
2004-04-08 22:25       ` [Caml-list] OpenGL Jon Harrop
2004-04-09  1:45         ` Brian Hurt
2004-04-09  2:57           ` Brandon J. Van Every
2004-04-09 10:57           ` Jon Harrop
2004-04-09 16:12             ` Brian Hurt
2004-04-10  4:32               ` Brandon J. Van Every
2004-04-10  4:59                 ` Kenneth Knowles
2004-04-10  8:17                 ` Nicolas Cannasse
2004-04-11  6:20                 ` Brian Hurt
2004-04-11  8:10                   ` skaller
2004-04-11  9:23                   ` Brandon J. Van Every [this message]
2004-04-11 12:08                     ` Jon Harrop
2004-04-11 12:01                   ` Jon Harrop
2004-04-09 12:52         ` Issac Trotts
2004-04-08 16:37   ` Anil Madhavapeddy

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=OOEALCJCKEBJBIJHCNJDOENGHAAB.vanevery@indiegamedesign.com \
    --to=vanevery@indiegamedesign.com \
    --cc=caml-list@inria.fr \
    /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).