7 ms·

"Any browser that doesn't implement WebGL will soon be considered crippled" Really? I don't think WebGL is that important. What's it really good for besides la

"Any browser that doesn't implement WebGL will soon be considered crippled" Really? I don't think WebGL is that important. What's it really good for besides laggy browser games? What's with the hype on browser games anyway? They're always going to perform much slower than native code. I don't see WebGL becoming such a critical aspect of browsing that the average user would consider IE "crippled" for not supporting it.

troymc 13y ago
Your challenge, should you choose to accept it, is to dream up an amazing and popular application of WebGL, now that a majority of web browsers will be supporting it. It might not be a game. Warning: imagination required.
- pbsdp 13y ago
  It's hard to dream big about the browsers getting the modern iteration of something we've had in some form since 1992.
  - andybak 13y ago
    You are assuming that a delivery mechanism can't be transformative.
  - ZeroGravitas 13y ago
    How does that not apply to every single thing on the web, whether text, image, animation, video, or interaction?
nitrogen 13y ago
Here's one application: http://youtu.be/zB7QEFCR1Zk?t=16m59s http://youtu.be/zB7QEFCR1Zk?t=16m59s
nailer 13y ago
ASM is only 2x slower than native (it was 10x prior to) and will be 1.5 soon. With a way better distribution model. Have you seen UE3 or UE4 demos?
- anon1385 13y ago
  >ASM is only 2x slower than native Only in wilfully misleading benchmarks. Allow use of SIMD and multithreading and asm.js can be as much as 50 times slower: http://cdn.arstechnica.net/wp-content/uploads/2013/05/native-code-game-640x480.png http://cdn.arstechnica.net/wp-content/uploads/2013/05/native... http://cdn.arstechnica.net/wp-content/uploads/2013/05/classic-native-v-optimized-v-asmjs-640x480.png http://cdn.arstechnica.net/wp-content/uploads/2013/05/classi...
  - nailer 13y ago
    Good point: re multithreading. I wonder if web workers could be used to resolve that?
nawitus 13y ago
It will soon be used for numerous business apps as companies are porting their native applications to work on browsers.
- jimmaswell 13y ago
  I just hope the desktop versions don't go away.

troymc 13y ago

Your challenge, should you choose to accept it, is to dream up an amazing and popular application of WebGL, now that a majority of web browsers will be supporting it. It might not be a game. Warning: imagination required.

pbsdp 13y ago
It's hard to dream big about the browsers getting the modern iteration of something we've had in some form since 1992.
- andybak 13y ago
  You are assuming that a delivery mechanism can't be transformative.
- ZeroGravitas 13y ago
  How does that not apply to every single thing on the web, whether text, image, animation, video, or interaction?

nitrogen 13y ago

Here's one application: http://youtu.be/zB7QEFCR1Zk?t=16m59s http://youtu.be/zB7QEFCR1Zk?t=16m59s

nailer 13y ago

ASM is only 2x slower than native (it was 10x prior to) and will be 1.5 soon. With a way better distribution model. Have you seen UE3 or UE4 demos?

anon1385 13y ago
>ASM is only 2x slower than native Only in wilfully misleading benchmarks. Allow use of SIMD and multithreading and asm.js can be as much as 50 times slower: http://cdn.arstechnica.net/wp-content/uploads/2013/05/native-code-game-640x480.png http://cdn.arstechnica.net/wp-content/uploads/2013/05/native... http://cdn.arstechnica.net/wp-content/uploads/2013/05/classic-native-v-optimized-v-asmjs-640x480.png http://cdn.arstechnica.net/wp-content/uploads/2013/05/classi...
- nailer 13y ago
  Good point: re multithreading. I wonder if web workers could be used to resolve that?

nawitus 13y ago

It will soon be used for numerous business apps as companies are porting their native applications to work on browsers.

jimmaswell 13y ago
I just hope the desktop versions don't go away.