From: "Nicolas Cannasse" <warplayer@free.fr>
To: "Brandon J. Van Every" <vanevery@indiegamedesign.com>,
<caml-list@inria.fr>
Subject: Re: [Caml-list] OpenGL
Date: Sat, 10 Apr 2004 10:17:12 +0200 [thread overview]
Message-ID: <000b01c41ed4$3a43fa10$19b0e152@warp> (raw)
In-Reply-To: <OOEALCJCKEBJBIJHCNJDGEMPHAAB.vanevery@indiegamedesign.com>
From: "Brandon J. Van Every"
Sent: Saturday, April 10, 2004 6:32 AM
> Minor points: OpenGL is generally regarded as a cleaner, easier to
> initialize API than DirectX. OpenGL is C, DirectX is C++. Either of
> those is an advantage or disadvantage depending on who you're talking to
> and the circumstances.
I think you're wrong here. DirectX is not C++. DirectX is COM, and then is C
compatible. However it have C++ wrappers to ease the syntax. The main
difference I can see between OpenGL and DirectX is that DirectX is directly
including all card vendors extensions and is always up-to-date (or even in
advance) with the high-end hardware, MS is doing a lot of cooperation with
NVidia and others and is putting a lot of efforts into DirectX - very good
documentation quality , very few bugs... among either - because they
understand how much it's important to keep being THE OS for playing games
(and, by reaction, developping games...). DirectX let you also play a lot
with cards capabilities, so you can tune better your code for some specific
cards. On the other hand, OpenGL is a more abstract layer, made for a
general-usage of 3D, that does implements card extensions - such as shaders,
which are main stream now - as extensions of itself. The community process
of OpenGL have not been enough reactive in order to keep up with DirectX (as
you said : where's 2.0 ?).
Regards,
Nicolas Cannasse
-------------------
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
next prev parent reply other threads:[~2004-04-10 8:19 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 [this message]
2004-04-11 6:20 ` Brian Hurt
2004-04-11 8:10 ` skaller
2004-04-11 9:23 ` Brandon J. Van Every
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='000b01c41ed4$3a43fa10$19b0e152@warp' \
--to=warplayer@free.fr \
--cc=caml-list@inria.fr \
--cc=vanevery@indiegamedesign.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