Somehow the site by itself was enough to crash firefox instantly. I tried it 3 times in a row, it consistently crashed on open, I'm using Firefox 18.0 on Ubuntu Precise, just in case the creator of the site runs around here.
Spider web hoorah. Runs surprisingly well on my ~2003 processor in Ubuntu with Firefox 14. In comparison, Gmail with hangouts is slower than this display.
Somewhat relatedly, after zenphoton.com I made a tool called High Quality Zen (HQZ) which uses a similar algorithm to do high quality off-line rendering. I made this video with it:
I thought about doing this but adding prisms to split the light and add colour, amazing that almost anything you can think of gets done somewhere on the internet if you wait long enough.
On my machine - firefox 21 running on linux - it completely obliterates my RAM and the machine starts swapping.
Edit: tried it with a separate profile with no extensions installed. Same story. Just drawing ten walls and letting it sit there not doing anything, it's actively leaking memory. Right now, with just that page open, the firefox process has RSIZE of 450MB and VSIZE of 1.4GB.
Edit²: tried with chrome Version 29.0.1521.3 dev. Same thing.
Piecewise, type-1, Wolter optics. From a useability perspective, I'd love the ability to either draw freehand lines, or splines. Also, a button / key to constantly keep the drawn lines visible would be nice. Amazingly cool little project though. http://zenphoton.com/#AAQAAkACAAEgdwEuACQA+wBdAPsA/wAAXQD7AK...
With zenphoton I really wanted to keep the user interaction model as simple as possible, since part of the 'zen' was in the drawing experience itself.
I made a more complex tool based on the same raytracing style, called High Quality Zen (HQZ). It has some support for representing curves as many small line segments with interpolated normals.
I realize. And I used that extensively. But if you're trying to draw lots of little links, or complex geometry, you often end up highlighting lines w/ undo, fixing a location in your head, and then trying to pick it again when they go invisible. A constant visibility option would just streamline that.
It's checking for features, not the version and browser. And as for features, UInt8ClampedArray is missing from IE (it was seemingly a late addition to Typed Arrays and might not have been picked up in time).
That being said, it appears that there is a slower alternative that works just as well, but someone would have to code up a workaround for IE in this case. I would have done it if I knew any JS (or CoffeeScript in this case).
Welp, that was way better than being productive. Shame it doesn't save the exposure level in the share link.