webgl

If you hand tune the JS and shader code WebGL can be very fast and short startup time.

Also it's already 5 months old and neither the website nore the Github or ChromeExperiments call it WebGL.

It's really high performance (uses Webgl by default and falls back to canvas if its unavailable).

WebGL can be very fast though hand tuned JS code and shader optimization is very important.

WebGL that more often than not crashes the browse, CSS animations that saturate an octocore...

This is the first time i played a really cool and addicting websocket/webgl game.

It's that ThreeJS abstraction library that's slow and why it's not okay to say it's a WebGL demo, it's a Three.js demo.

It's an implementation detail -- whether it uses ThreeJS, stackgl, or your home-brew library, it still uses WebGL as its primary technology.

Mozilla has publicly stated they aren't interested and are going with WebGL 2.0 instead.

Open/WebGL has a lot of misinformation across the web, so it's great to be able to learn from people who have more experience.

I ran into the same issue trying to use a video as a texture in WebGL.

The font post and the WebGL demo are both the sort of thing users have seen a lot of, and the other two were pretty specialized.

Though you may have read the title as "game written in webgl" I'm pretty sure it's meant to be read as "game using webgl".

It's based on Three.js, calling it "WebGL" is false advertising.

I decided to use a "picking" model and encode geometry IDs in base 255 (4+ billion IDs) into the color buffer and provide a consistent API for both the DOM and WebGL renderer.