News for hackers. Stuff that matters.
Re:Microsoft has joined Khronos, WebGL working group by ksk on Monday August 11, 2014 @03:53AM (#8162373)
It's interesting to see so many people supporting webGL. Other than the "same X, but now X runs inside a browser" novelty aspect, I have yet to see any evidence that webGL does anything useful. To be fair, in this respect, it's no different from flash or javascript or any of the other technologies that people use to produce inferior replacements of native applications.
Re:Microsoft has joined Khronos, WebGL working group by pjc50 on Monday August 11, 2014 @08:23AM (#8162943)
Running in a browser offers an (imperfect) security sandbox on a desktop PC, so people don't have to download and run untrusted executables. It also offers portability, and a certain amount of "copy protection".

If your application is inherently networked, it works just fine in the browser.

Re:Microsoft has joined Khronos, WebGL working group by ksk on Monday August 11, 2014 @10:45AM (#8163450)
The sandbox is a feature afforded by the underlying OS and CPU architecture. I didn't quite understand your point.

With regards to game distribution, I don't see any particular advantage that a browser has over something like Steam. You don't need to download multiple gigabytes either. You could design a game to stream levels/assets/etc on-demand. In any case, even with webGL, a game would need to do that.

Re:Microsoft has joined Khronos, WebGL working group by pjc50 on Tuesday August 12, 2014 @09:30AM (#8167628)
The sandbox is a feature afforded by the underlying OS and CPU architecture

Absolutely not; the sandbox of Javascript apps is entirely within the browser. The CPU architecture may theoretically prevent a userspace app from breaking into ring 0, but that's not the interesting thing; you're trying to prevent random apps from gaining access to all the tasty data in userland.

"Please do not download and run random executables" is a lesson that security people have been trying to get across for a while. Running a native game executable involves trusting it not to be malware. Running a webgl or HTML5 game does not.

(The sandboxing of webgl may be dodgy, which is a weakness here.)

Re:Microsoft has joined Khronos, WebGL working group by ksk on Wednesday August 13, 2014 @09:09AM (#8172675)
>Absolutely not; the sandbox of Javascript apps is entirely within the browser. The CPU architecture may theoretically prevent a userspace app from breaking into ring 0, but that's not the interesting thing; you're trying to prevent random apps from gaining access to all the tasty data in userland.

I don't know why you felt compelled to state a categorical denial when the facts dispute it. Please read up on how security tokens work in Windows, for e.g.

http://msdn.microsoft.com/en-us/library/bb625957.aspx

> Running a native game executable involves trusting it not to be malware. Running a webgl or HTML5 game does not.

There is no difference between those two executions in modern operating systems that implement mandatory access control.

Re:Microsoft has joined Khronos, WebGL working group by lobo_tuerto on Monday August 11, 2014 @01:17PM (#8164139)
The thing is, it is in your browser. A machine without an internet browser is unheard of, the internet browser is everywhere. You can't say the same for Steam.

It is convenient. What is it not understandable about that?

Re:Microsoft has joined Khronos, WebGL working group by ksk on Monday August 11, 2014 @01:43PM (#8164288)
>The thing is, it is in your browser.

I already excluded this part from my criticism. Please read my original comment.

>You can't say the same for Steam.

So, the solution to that is to create something like Steam, but better. Choosing an inferior technology is the opposite of a solution.

I predict that advertisers are going to overuse webGL just like flash. We're going to see webGL blockers crop up the minute it gets any kind of traction. Certainly, I am not going to subject my machine to another malware vector.

Re:Microsoft has joined Khronos, WebGL working group by lobo_tuerto on Wednesday August 13, 2014 @11:57AM (#8173497)
Technology evolves, and if you have been paying attention to browsers they have been getting better and better, and they will keep doing it.
Re:Microsoft has joined Khronos, WebGL working group by _random_ on Monday August 11, 2014 @02:21PM (#8164455)
It has three purposes:

- potential future GUI solution to end the sad HTML5-only lock of the web;

- useful for quick dirty prototypes/samples for full OpenGL tutorials;

- generating HN karma: just find any old OpenGL sample (quality doesn't matter), convert it to WebGL, post on HN (make sure to add 'WebGL' and 'JavaScript' to title) - ka-ching!

Re:Microsoft has joined Khronos, WebGL working group by ollybee on Monday August 11, 2014 @09:08AM (#8163082)
Re:Microsoft has joined Khronos, WebGL working group by ksk on Monday August 11, 2014 @11:01AM (#8163527)
Thanks for the link, but if anything, it convinced me further that webGL continues to be an inferior alternative, in performance, resource consumption and feature parity, to existing, established 3D APIs like OpenGL/Direct3D/etc.

Also, I do think the author is joking with regards to it being 'the best tested 3D API'. The author backs up this absurd claim with some 'thousands of tests' comment. Hello? Have they never visited shadertoy? Even trivial shaders cause webGL to crash because of the poor implementation quality. I refuse to believe that a person who has had any experience shipping OpenGL ES on multiple platforms could make such a statement.