On the Subject of OpenGL 2.0
zendal writes "The danger with pixel shaders and vertex shaders is that there is no standard for programmability of graphics hardware. A schism has formed within DirectX between the competing demands of GPU makers Nvidia and ATI. Noted analyst Jon Peddie gives THG an exclusive first look at a White Paper on how OpenGL 2.0 is trying to bring stability and open standards to programmable graphics and GPUs."
look?.. whatever.. :-)
anyone wanna comment on this?
Not quite first, but second isn't bad either.
EVERYONE needs to click that link. The integrity of your file system depends on it!
i want to kill
everyone
satan is good
satan is my pal
I know this is off-topic, but for how much people used to knock Tom's saying that he's an invalid source for tech news there sure as hell are a lot of people submitting stories from there.
;p
Moderators, do your damage
I was at my machine, being assfucked, when I got email congratulating me on the success of my anal streching.
LOL this moron thinks we would actually click on the link..what a foo foo
-- Powered By Linux
http://www.3dlabs.com/support/developer/ogl2/index .htm
I came across this a while back.
OpenGL 2.0
Welcome to the download site for the first versions of the OpenGL 2.0 white papers. Since 3Dlabs embarked on this project in the summer, we've received extremely positive feedback - from other OpenGL ARB members, from software developers and from the graphics community at large. The prevailing sentiment is that OpenGL needed to be updated to respond to the trend toward programmable graphics hardware. And there was a good deal of support for taking this opportunity to tune up some other aspects of OpenGL, which has been around for the better part of 10 years.
Our goals for OpenGL 2.0 are to add support for pixel and fragment shaders, improve memory management and give applications more control over the rendering pipeline. In doing so, we still will provide compatibility with OpenGL 1.3 - so older applications will run on graphics accelerators with OpenGL 2.0 drivers.
These white papers are the first step in a process that will lead to a significant enhancement of the OpenGL API. The white papers will be revised to reflect the input of numerous OpenGL 2.0 participants: other graphics board developers, DCC software developers, CAD software developers, imaging software developers, game developers and academia. There will be a revision to these white papers and then we'll start work on the OpenGL 2.0 specification with other OpenGL ARB members. We're expecting to have a specification available in the spring of 2002.
If you are interested in providing input to this process - either in the form of e-mail or through conversation, you must sign the OpenGL 2.0 Review Agreement that is included in the ZIP file. While the terms of the Agreement are quite open, you still should have your legal counsel review it. Please fax the signed Agreement to John Schimpf at 408-530-4701.
If you are simply interested in reading the white papers, you do not need to sign the Agreement.
I'd like to thank the 3Dlabs team for their hard work in producing the white papers on a very aggressive schedule, and reviewers from Alias|Wavefront, Apple, ATI, Discreet Logic, id Software, Nvidia, PTC, SGI, SoftImage, the Stanford Graphics Lab, Vital Images and others.
I'm confident that OpenGL 2.0 will meet the needs of graphics applications developers for many years to come.
Regards,
John Schimpf
john.schimpf@3dlabs.com
Dr. Suess: 'Gandalf, Gandalf! Take the ring! I am too small to carry this thing!' 'I can not, will not hold the One.
WTF? I need some more horizontal scrolling here. I need the page to be wide like cmdrtaco's fiance.
Dumbass!!
MPEG was longtime THE de facto standart for video.. now they want a penny _EVERYTIME_ a film is played.. sorry mpeg, i'll never use you again. DivX owns! =)
The Quake III Arena 1.31 patch has been released. The release notes include the following:
/etc/fstab. By the way, if you screw that up, you are really fucked.
Linux only:
fixed sound crash, going around memset bug in glibc i586/i686
Wondering how a bug could exist in such a fundamental basic function such as memset, we contacted Heinous Turdballs of Linux fame, and he was kind enough to give a few minutes of his time.
Q: Thanks for your time in answering some questions for us
A: No problem. As you know, I am umemployed and have no life, which is of course how I got involved in Linux in the first place.
Q: OK, Mr. Turdballs. By the way, do you mind if I call you 'Dirty GNU Hippie'?
A: I would rather you didn't. I prefer the term 'Dirty Linux Hippie'. As you know, my ratty and nasty hairdo, my rancid steaming armpits and my putrid stench of body odor makes me qualified, I think.
Q: I quite agree. Can you tell us about the memset bug?
A: Sure. We dont really know who is responsible for the bug. We don't know who is making changes, why they make them, or when.
Q: Hmm.. sounds chaotic!
A: It sure is. But Linux is free!!! We are dirty smelly GNU hippies with natty greasy long hair, enjoying the FREE LOVE of GNU software!
Q: Come to think of it, Linux sure does crash alot.
A: Yeah, but that will be fixed in the service pack - er, I mean kernel release. We also have support for some new device drivers that came out 2 years ago. You just have to recompile your kernel with the correct command line switches, after configuring your make file and making the correct edits to
Q: Sounds good. So, how do you organize who is working on Linux?
A: Mostly we don't. We pretty much let anyone have at it with the code base. We figure at some point, someone who actually knows something about operating systems will do some work on it. It has to happen eventually, its like a million monkeys banging on a million typewriters. Literally.
Q: That's great. What normally happens?
A: Normally someone comes in and fucks everything up completely, but we don't know who they are because we never actually talk to anyone who is making changes to the code. We assume that if you are capable of signing up for a Hotmail account, you must be pretty good at computers and you should be a tech lead in a major open sores project.
Q: Open sores?
A: Yes, I am sure you have heard of it. Its free, therefore its good. Check out sourceforge.net, where bad project ideas go to a quiet and lonely death when the developers realize that 12 year old kids should not be SQA leads when they are constantly getting atomic wedgies because they wear shirts saying "Put Linux Anywhere".
Q: OK, Back to the topic. Whats a typical day in the life of a Linux developer?
A: Usually his mom wakes him up in time to catch the school bus, like 8:00. We encourage this because we want the developers to be well edumacted.
By the time he gets home at 2:00 (the Linux enthusiast does not participate in socalled "extra cirricular" activities, or worry about being "well rounded" and does not have a "social identity" or "play well with others") he has been beaten up a few times for wearing a "I GNU SPOCK" tshirt.
Then, to take out his frustration, he hammers away at the keyboard for a few hours. If the resultant code compiles, he will go ahead and check it in. Then mommy tucks him in for the night.
Q: Interesting. So who will be in charge of resolving the memset bug?
A: We have a nice prospect in mind. He has a strong background in manual labor and performing menial tasks. I'm not sure what his name is but he has a hotmail account, dAsUpAhZillAZ99@hotmail.com.
Q: Sounds great. I'm looking forward to it!
A: Just keep reading slashdot, where are the pimply nerds congregate. You may get assaulted by some homosexual linux zealots, but you will learn to like it.
Q: Sounds like fun!
A: Also hang out at sourceforge.net, where bad project ideas go to a quiet and lonely death among the other dirty GNU hippie projects.
Q: Thanks for your time!
A: Tell commander tuna taco I said I will pay in full after I get a real job. Then I will be back for another taco-snotting.
You can scare a person by confusing his mind!
ba ba ba ba ba ba ba ba ba ba ba!
Let's start one step at a time!
ba ba ba ba ba ba ba ba ba ba ba!
John and John forever!!!
Can you spell F-A-N-B-O-Y?