Anyhow I’m fan of such experiments and really like UnConeD‘s ways.

http://blog.papervision3d.org/

In the past year, the project has made some amazing progress.

That, I can’t argue with :)

I still would like to have a mature 3D API to use for a serious web application someday though. On that note, flash 10 isn’t looking too shabby.

Obviously, this is slow and experimental, and in no way a replacement for real 3D support in Canvas, Java or Flash. But, that doesn’t mean that this isn’t an interesting experiment: when Canvas 3D finally lands, we’ll still be stuck with old browsers. This little toy was meant to answer a couple of questions… How good does this fake technique look? How detailed does it need to be? Can typical canvas implementations handle it? The only way to do that was to try it out.

In fact, I find it funny that Ajaxian uses the word ‘library’ to refer to this, when this was never meant as such. They cut out the last paragraph of my post where I clearly said it was just a curiosity and nothing serious. It’s weird how on the web, every piece of code seems to be judged on how other people can re-use it. I’m guessing this is because there is a large contingent of ‘developers’ who don’t in fact write any code themselves. They just glue together existing libraries and widgets.

For me, this was just a fun distraction. But I’m equally comfortable hand-rolling assembly code for triangle rasterizers, or stringing together shaders to run on the GPU. I’m sure I’m not the only programmer out there who likes coding in scripting languages for how quickly you can build things, rather than ultimate usefulness of the end product.