3d engine on js + canvas
Once I came across a foreign article about the bright future of Canvas and WebGL, and there was a picture in this article with a “3d teapot” drawn using canvas, it struck me well, I realized that I had to do something similar, and did .

When adjusting for JavaScript performance, the z-buffer implemented in polygon, not pixel. Everything looks good until there is no mutualintersection of model penetration.
Export of the model comes directly from 3ds max, through ASCII Scene Export.

Should work in all good latest browsers. I added a “speedometer” or “FPS meter” or “FPS meter” to the demo, well, you understand - in the upper right, the “current FPS” - is determined by the last 10 and renders, and the “average” by all renders from the very beginning of the script, after a couple of minutes the average value stops fluctuating and shows the true value of the speed of the browser.
I have the following alignment of forces: I

used explorercanvas for ie
- it upsets the lack of canvas support in ie9 preview, by the first impression of jit it works very well.
What is the future for this technology? Someone sees this as the basis for future online games, someone is a competitor to flash, someone is an unnecessary tag in html, but what do you think? So far, the only application that I have found is to test the speed of browsers.
PS WebGL is not used yet, but I plan to fasten it and compare the results.
UPD1: (browser versions)
Chrome 5.0.375.53 beta
FireFox 3.6.3
Opera 10.51
UPD2: (details)

UPD3: Habraffect whistled out vps, ... tightened the nuts, kicked and it was back in action.
UPD4: Added the results of FF 3.7 Alpha 4
(thanks for the results in the comments, but I was thinking, if I add them to the summary statistics, then it will not reflect the real picture, because everyone has different hardware - it’s weaker / more powerful)

When adjusting for JavaScript performance, the z-buffer implemented in polygon, not pixel. Everything looks good until there is no mutual
Export of the model comes directly from 3ds max, through ASCII Scene Export.

Should work in all good latest browsers. I added a “speedometer” or “FPS meter” or “FPS meter” to the demo, well, you understand - in the upper right, the “current FPS” - is determined by the last 10 and renders, and the “average” by all renders from the very beginning of the script, after a couple of minutes the average value stops fluctuating and shows the true value of the speed of the browser.
I have the following alignment of forces: I

used explorercanvas for ie
- it upsets the lack of canvas support in ie9 preview, by the first impression of jit it works very well.
What is the future for this technology? Someone sees this as the basis for future online games, someone is a competitor to flash, someone is an unnecessary tag in html, but what do you think? So far, the only application that I have found is to test the speed of browsers.
PS WebGL is not used yet, but I plan to fasten it and compare the results.
UPD1: (browser versions)
Chrome 5.0.375.53 beta
FireFox 3.6.3
Opera 10.51
UPD2: (details)

UPD3: Habraffect whistled out vps, ... tightened the nuts, kicked and it was back in action.
UPD4: Added the results of FF 3.7 Alpha 4
(thanks for the results in the comments, but I was thinking, if I add them to the summary statistics, then it will not reflect the real picture, because everyone has different hardware - it’s weaker / more powerful)