News for hackers. Stuff that matters.
Re:Microsoft tries to step on WebGL, stumbles on its own feet by ZeroGravitas on Thursday June 23, 2011 @07:17AM (#2687450)
"there are so many security holes in web browsing already, why do you begrudge us a few more?"

I think this is a valid argument.

You see a lot of arguing about things online where something being slower, more expensive, harder to use, less secure, more radioactive etc. is presented as a case-winning argument, without anyone bothering to quantify the problem or put it in context.

The world isn't build on absolutes, unless you can guesstimate how much less secure or more radioactive something will be (a banana worth or a chernobyl worth) then why should I care? If we're really taking the absolutist stance that nothing that introduces a potential security issue (or the slightest additional radioactivity) is allowed then we might as well abandon all technology and go back to living in caves.

At least try to make a case that WebGL, if not strangled at birth, will create a noticeably less safe web than would exist in a world with all the current issues, all the ones associated with Silverlight and Flash using GPUs, and all the new issues from whatever other features are added to browsers, computers or smartphones over the same timeframe.

Re:Microsoft tries to step on WebGL, stumbles on its own feet by yaakov34 on Thursday June 23, 2011 @10:11AM (#2687901)
There is also such a thing as opportunity cost. Web browsing, and the online world in general, is execrably insecure. A day doesn't pass without a high-profile target being owned by some attention-seeking script kiddie. I can only imagine what serious malware syndicates, who don't advertise themselves to the whole world, have been up to.

And what does the web development world want to do? It wants WebGL and a bunch of other shiny new APIs. As a user, I am just annoyed by this. I also work on stuff that needs to be secure, and if I wanted to add bells and whistles and dancing monkeys and make security worse instead of fixing it, I'd be told "no." Actually, I would never propose it. Now I realize that the complaint is directed at no one in particular, but I still can't help being annoyed.

Now, this WebGL thing in particular has every security researcher saying "don't expose GPU drivers to this." And the web developers' response is essentially "nyah nyah, you're getting this anyway and you can't stop it". Or "what are you, a Microsoft stooge? They are doing it too." Or just "go away and stop harshing my mellow" (around here, the way of doing that is with a downvote). Well, OK, enough out of me on this subject.