Support of the feature by the video card is mandatory. Use of the feature by the game is not.
At least, that's how I understand it.
That aside, am I the only person who remembers reading this "bomb" months back? The plan was that instead of checking for individual features (and coding around their lack case-by-case, like we will still get to do with OpenGL) the developer would check for a DirectX version, leaving fewer opportunities for wonky bugs from weird support combinations.
-:sigma.SB
(Disclaimer: I am a game developer who exclusively uses OpenGL for hardware 3D and I fully intend never to write a single line of DirectX code. Ever.)
It wouldn't even recognize my Radeon 9800 Pro Mac Edition. I spent $250 on that thing only to get fundamentally broken bus management on OSX and no 3D at all on Linux.
Building a Dyson sphere as small as Earth would require a pretty small star. Even if we assume that natural nuclear fusion is possible with such a small mass, it would run through its fuel pretty quick.
Besides, I think we'd know if massive-scale nuclear fusion was taking place in the Earth's core.
My room has an old Dell PowerEdge sitting in the corner. It's so loud, I had to turn my music up enough to shake the floor and freak the neighbor's dog before I could tell what I was playing.
By this type of application, are you referring to networked applications, for which cpu time is in no way a limiting factor?
Sure, a processor capable of several thousand CPU cycles per transmitted bit can easily handle the load, even in Java. (3GHz CPU, 1.5Mb "broadband") Now scale that to hundreds of gigabits.
I, for one, am glad that proprietary drivers are so poor, because it encourages free drivers to be written instead.
These are not only free-er, but usually of better quality too.
I'm still waiting for a Free 3D driver for my Radeon 9800 Pro Mac Edition. (Not for much longer, though, since I'm moving to an all-OSX setup on my next computer...)
-:sigma.SB
P.S. no, the R3xx DRI code in the Xorg tree did not work. Not even accelerated 2D.
Until about a month ago, I was getting ~10 spam emails per day through the filters. All of them the same, obviously spam, subject lines ("RX_MEDS no pr3s needed" etc.) which on the one hand made me wonder how they were getting through but on the other made it easy to deal with them. Now I get one of those a week.
In my entire history at GMail, though, I've gotten one mis-marked legitimate message; and if someone else had been reading my incoming messages he would have thought it was spam too.
In this day and age, a young child is exposed to violence on television, in movies, and in video games. Much emphasis is placed on the glory and excitement of opening fire on the enemy with oversized gatling guns and flashy rocket launchers, but no parent is willing to do much more than say "violence is bad" to counteract it.
A psychopath is a psychopath, but some children are turning into them who didn't have to because of the way they're raised. (I almost did.) Images that should be disturbing are now commonplace. This can't be a good thing.
Also, from a Darwinian perspective, it seems strange to emphasize same-species killing over reproduction.
-:sigma.SB
(I'm project lead on a war sim, with plenty of blood. I don't think that violence in media is necessarily a bad thing, I just think its influence on young children is often underestimated here.)
The graphics are really bad. SMB and the original Zelda have clean crisp graphics. Ocarina of Time have untold amounts of problems with aliasing and stuff like that. It's almost unplayable now that the standard has been raised so far by modern games and consoles.
You think hand-drawn 16-color sprites at 256x224 resolution more advanced than 32-bit 3D with console-straining textures, animations, and effects at 320x240?
If the resolution bugs you so much, get an emulator and turn the res up.
-:sigma.SB
(btw, I'm playing it right now. if you think the N64 was bad, try playing the original Metal Gear Solid.)
It increases the complexity and requirements of implementing the attack.
With a GET request, all you need is for the victim's browser to visit the URL. You could hide a link, or even put it as the SRC for some other tag. You could hide it in an <IMAGE>, or even a <LINK>. (Or, as another poster pointed out, in an invisible <IFRAME>.)
With POST, on the other hand, you have to get the victim to submit a deliberately crafted form. With JavaScript you could do this automatically, but that's not nearly as easy as <LINK REL="stylesheet" TYPE="text/css" SRC="http://www.bankofsomethingorother.com/account .asp?action=transfer&amount=1000.00&dest=716281"/>.
One way to completely protect against this "vulnerability" with currently implemented technology is to be really strict about Referer headers. No header = request denied. Source other than same site = request denied. Problem solved, unless modern browsers have some screwed up behaviors I don't know about.
I'm developing (under contract) an open source, ultra-modular game engine. I originally intended to release it under the GPL, but upon closer examination of the license determined that it would then be impossible to make a game or other addon package licensed under anything but the GPL.
So now, rather than use a less restrictive license directly, I will have to release under a customized GPL (similar to the LGPL) which allows for linking with "proprietary" packages and set up a very elaborate and clumsy subsystem to prevent GPL and "proprietary" packages from being loaded at the same time, in stark contrast to the elegance of the rest of the code.
cue FSF zealots telling me that I am morally wrong for supporting proprietary software in this way
On top of that, I had to sell the idea of not using the vanilla GPL to my boss, who was freaking out about how that would keep it out of Debian forever.
If you want the benefits and bootstrapping of someone else's free code, play by the GPL's rules. Otherwise, write it yourself.
What if I'm writing code and I want others to benefit and bootstrap from my code without the GPL's restrictions on what they can do? By using a less restrictive license, I forbid them from releasing their own code under the GPL. The LGPL doesn't always cut it for this case, either.
Slashdot Mirror
Support of the feature by the video card is mandatory. Use of the feature by the game is not.
At least, that's how I understand it.
That aside, am I the only person who remembers reading this "bomb" months back? The plan was that instead of checking for individual features (and coding around their lack case-by-case, like we will still get to do with OpenGL) the developer would check for a DirectX version, leaving fewer opportunities for wonky bugs from weird support combinations.
-:sigma.SB
(Disclaimer: I am a game developer who exclusively uses OpenGL for hardware 3D and I fully intend never to write a single line of DirectX code. Ever.)
You're thinking of Carmageddon, and the blood was only green in the versions released in some parts of Europe.
-:sigma.SB
It wouldn't even recognize my Radeon 9800 Pro Mac Edition. I spent $250 on that thing only to get fundamentally broken bus management on OSX and no 3D at all on Linux.
-:sigma.SB
And if they do, you'll demand that they give you uncompressed 24-bit recordings as a justification for your continued piracy.
-:sigma.SB
Resistance: Fall of Man.
Speaking as someone who hated the PS3, it blew me away.
If I were filthy rich I'd even buy a PS3, just to play it.
-:sigma.SB
There are better ways to enjoy yourselves than by imbibing a dangerous psychoactive chemical.
-:sigma.SB
Sorry to ruin the gag, but probably the Visual C compiler.
-:sigma.SB
Building a Dyson sphere as small as Earth would require a pretty small star. Even if we assume that natural nuclear fusion is possible with such a small mass, it would run through its fuel pretty quick.
Besides, I think we'd know if massive-scale nuclear fusion was taking place in the Earth's core.
-:sigma.SB
Augmenting a single damaged center of the brain is difficult with the technology of today but not a long-term impossibility.
Completely reconstructing a person's memories and personality when their brain has turned into slurry is not possible without time travel.
Which is pretty much exactly what the parent poster said.
-:sigma.SB
My room has an old Dell PowerEdge sitting in the corner. It's so loud, I had to turn my music up enough to shake the floor and freak the neighbor's dog before I could tell what I was playing.
Sleeping there is fun. :|
-:sigma.SB
Sure, a processor capable of several thousand CPU cycles per transmitted bit can easily handle the load, even in Java. (3GHz CPU, 1.5Mb "broadband") Now scale that to hundreds of gigabits.
IAAP
-:sigma.SB
Why dedicate a port when you can just add another generic port for whatever the frell the user wants plugged in?
-:sigma.SB
America, behind another country in $(SCIENCE)? SHOCKING! :P
-:sigma.SB
What about unstable open source kernel drivers?
-:sigma.SB (who went through over 60 reboots trying to get non-crashing 3D on his iBook's Rage 128 before finally giving up)
I'm still waiting for a Free 3D driver for my Radeon 9800 Pro Mac Edition. (Not for much longer, though, since I'm moving to an all-OSX setup on my next computer...)
-:sigma.SB
P.S. no, the R3xx DRI code in the Xorg tree did not work. Not even accelerated 2D.
The Paradox of Choice: Why More Is Less
-:sigma.SB
That is the intention of TPM.
-:sigma.SB
Until about a month ago, I was getting ~10 spam emails per day through the filters. All of them the same, obviously spam, subject lines ("RX_MEDS no pr3s needed" etc.) which on the one hand made me wonder how they were getting through but on the other made it easy to deal with them. Now I get one of those a week.
In my entire history at GMail, though, I've gotten one mis-marked legitimate message; and if someone else had been reading my incoming messages he would have thought it was spam too.
-:sigma.SB
The 'G' in GTK stands for "gimp," FYI.
-:sigma.SB
It doesn't require registration but it does require you to accept 7 cookies from them.
-:sigma.SB
In this day and age, a young child is exposed to violence on television, in movies, and in video games. Much emphasis is placed on the glory and excitement of opening fire on the enemy with oversized gatling guns and flashy rocket launchers, but no parent is willing to do much more than say "violence is bad" to counteract it.
A psychopath is a psychopath, but some children are turning into them who didn't have to because of the way they're raised. (I almost did.) Images that should be disturbing are now commonplace. This can't be a good thing.
Also, from a Darwinian perspective, it seems strange to emphasize same-species killing over reproduction.
-:sigma.SB
(I'm project lead on a war sim, with plenty of blood. I don't think that violence in media is necessarily a bad thing, I just think its influence on young children is often underestimated here.)
Unless you've found a server whose bandwidth is lower than yours.
Also, 10MB is not big enough for a reliable test. I'll arbitrarily say 200MB minimum for a fair test.
-:sigma.SB
You think hand-drawn 16-color sprites at 256x224 resolution more advanced than 32-bit 3D with console-straining textures, animations, and effects at 320x240?
If the resolution bugs you so much, get an emulator and turn the res up.
-:sigma.SB
(btw, I'm playing it right now. if you think the N64 was bad, try playing the original Metal Gear Solid.)
It increases the complexity and requirements of implementing the attack.
With a GET request, all you need is for the victim's browser to visit the URL. You could hide a link, or even put it as the SRC for some other tag. You could hide it in an <IMAGE>, or even a <LINK>. (Or, as another poster pointed out, in an invisible <IFRAME>.)
With POST, on the other hand, you have to get the victim to submit a deliberately crafted form. With JavaScript you could do this automatically, but that's not nearly as easy as <LINK REL="stylesheet" TYPE="text/css" SRC="http://www.bankofsomethingorother.com/account .asp?action=transfer&amount=1000.00&dest=716281" />.
One way to completely protect against this "vulnerability" with currently implemented technology is to be really strict about Referer headers. No header = request denied. Source other than same site = request denied. Problem solved, unless modern browsers have some screwed up behaviors I don't know about.
-:sigma.SB
Here's how.
I'm developing (under contract) an open source, ultra-modular game engine. I originally intended to release it under the GPL, but upon closer examination of the license determined that it would then be impossible to make a game or other addon package licensed under anything but the GPL.
So now, rather than use a less restrictive license directly, I will have to release under a customized GPL (similar to the LGPL) which allows for linking with "proprietary" packages and set up a very elaborate and clumsy subsystem to prevent GPL and "proprietary" packages from being loaded at the same time, in stark contrast to the elegance of the rest of the code.
cue FSF zealots telling me that I am morally wrong for supporting proprietary software in this way
On top of that, I had to sell the idea of not using the vanilla GPL to my boss, who was freaking out about how that would keep it out of Debian forever.
What if I'm writing code and I want others to benefit and bootstrap from my code without the GPL's restrictions on what they can do? By using a less restrictive license, I forbid them from releasing their own code under the GPL. The LGPL doesn't always cut it for this case, either.
-:sigma.SB