From: Tomas Carnecky <tom@dbservice.com>
To: Dirk <d_i_r_k_@gmx.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Gaming Interface
Date: Mon, 08 Jan 2007 22:57:32 +0100 [thread overview]
Message-ID: <45A2BE4C.7030109@dbservice.com> (raw)
In-Reply-To: <45A22D69.3010905@gmx.net>
Dirk wrote:
>
> How about having a simple Game API like SDL included in the Kernel and
> officially announce the promise to change it only once every couple of
> years?
>
A new API would be counter-productive! There's X11/OpenGL for graphics
and OpenAL for sound, both APIs widespread even in the windows world and
also on BSD and all other flavors of UNIX. X11/OpenGL hasn't changed for
years (X11R6 has been released around 1985 IIRC).
The whole point of X11 is that anyone can implement a server, the spec
is open to anyone, and once you write a X11-compliant client it will run
on any UNIX/Linux computer.
Now if you introduce a special API for the Linux kernel, the game
developers would have to create two versions, one for Linux and one for
all other UNIXes. But more realistically, they'd just stick with the
plain old X11/OpenGL/OpenAL design because not everyone will have this
new kernel and they'd still have to release two versions for Linux: one
for the new kernel and one for the older computers.
Linus already stated several times that the kernel ABI is not stable! It
will change, and it's the responsibility of userspace tools/libraries to
provide a stable API.
So, to answer your question: We already have a simple API. One that has
been stable for 10+ years now and won't be changing anytime soon.
tom
next prev parent reply other threads:[~2007-01-08 21:38 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-08 11:39 Gaming Interface Dirk
2007-01-08 10:43 ` Trent Waddington
2007-01-08 12:13 ` Dirk
2007-01-08 11:17 ` Jay Vaughan
2007-01-08 13:04 ` Dirk
2007-01-08 14:09 ` Helge Hafting
2007-01-08 15:36 ` Dirk
2007-01-08 15:11 ` l.genoni
2007-01-08 19:31 ` Jan Dittmer
2007-01-09 7:14 ` Dirk
2007-01-09 6:16 ` Trent Waddington
2007-01-09 7:07 ` Adrian Bunk
2007-01-09 7:10 ` Trent Waddington
2007-01-09 16:08 ` Lennart Sorensen
2007-01-09 23:02 ` Valdis.Kletnieks
2007-01-09 23:05 ` Lennart Sorensen
2007-01-09 9:50 ` Kasper Sandberg
2007-01-09 12:15 ` Jesper Juhl
2007-01-09 16:07 ` Lennart Sorensen
2007-01-08 19:57 ` Adrian Bunk
2007-01-09 7:16 ` Dirk
2007-01-09 7:00 ` Adrian Bunk
2007-01-09 7:08 ` Trent Waddington
2007-01-09 9:51 ` Kasper Sandberg
2007-01-09 4:40 ` Kasper Sandberg
2007-01-09 7:22 ` Dirk
2007-01-09 9:48 ` Kasper Sandberg
2007-01-09 12:10 ` Helge Hafting
2007-01-09 16:04 ` Lennart Sorensen
2007-01-09 16:51 ` Adrian Bunk
2007-01-09 21:14 ` Akula2
2007-01-08 14:47 ` Alistair John Strachan
2007-01-08 20:39 ` Jan Engelhardt
[not found] ` <a06230924c1c7d795429a@192.168.2.101>
2007-01-08 11:42 ` Dylan Taft
2007-01-08 21:57 ` Tomas Carnecky [this message]
[not found] <fa./yEu+Q5zfyi+9Dt6KeRH/0YTv6M@ifi.uio.no>
[not found] ` <fa.lZ5ow3GVFhmIN84swduaYc/QGC8@ifi.uio.no>
[not found] ` <fa./w7HN6qfHdRrvVr4gQ41Yr6D2Zs@ifi.uio.no>
[not found] ` <fa.wzIAazh/K3RXZGwCv85z7hMkX9w@ifi.uio.no>
[not found] ` <fa.QdkEYH0MeusxZdKe4kSh6Svj6dI@ifi.uio.no>
[not found] ` <fa.j23ZZ5CMmxfxN0vEdIJJTHQ1MeE@ifi.uio.no>
2007-01-10 0:48 ` Robert Hancock
2007-01-10 11:06 ` Akula2
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=45A2BE4C.7030109@dbservice.com \
--to=tom@dbservice.com \
--cc=d_i_r_k_@gmx.net \
--cc=linux-kernel@vger.kernel.org \
/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