It's inevitable (and Apple, Adobe, and Mozilla seem to be pushing hard here), but I found a fun twist on Google's part: pixel shaders for the web! I heard Adobe's pixel shader support (PixelBender) is iffy distribution-wise, but O3D (... and thus likely WebGL?) seem like a happier route. The downer is that this means HLSL is rearing its ugly head even further.
Fun implication on my browser-based browser hackery -- we can prototype naive hardware accelerated rendering within the browser!
A lot more fun on the Google gallery for O3D.
Tuesday, February 16, 2010
Monday, February 1, 2010
I finally understand [[Prototype]]
... except for why "myFun.prototype = null" acts like "myFun.prototype = Object.getPrototypeOf({})" but "myObj.__proto__ = null" does not. I prefer the latter as it takes us way closer to enabling wrapper-based (with no rewriting / static analysis) capability security.
Hopefully post tomorrow about a scary class of attack Dave Wagner pointed out as exploitable in my code: platform exceptions that are outside of standard language semantics yet still are script level.
Hopefully post tomorrow about a scary class of attack Dave Wagner pointed out as exploitable in my code: platform exceptions that are outside of standard language semantics yet still are script level.
Subscribe to:
Posts (Atom)