I posted the Atlas/Opera text also on the Opera Community forums. JeroenH provided with some specifics regarding the issues, and it seems to be related to JavaScript engine used in Opera:
Some Opera developers went to MS a few days ago. I guess they also talked about Atlas. The design of Atlas is broken, since they use proprietary features to emulate other proprietary features, not quite a good foundation to build on.
But I believe there is a chance Opera will add support for getters and setters (although I don’t like them), since Opera is working on a JS 2 implementation for 2007 (Opera 10?). JS 2 includes getters and setters (but not defineGetter and defineSetter if i’m not mistaken). Maybe they’ll do it gradually, just like mozilla is slowly getting ready for js 2 with js 1.7.
I salute Opera for striving for standard-perfect implementations, but sometimes it makes me wonder, are these puristic methods actually making life harder for us developers and end users, not the other way, as intended?
In some sence, this relates to my earlier post (in Finnish) regarding Atom vs. RSS. In it, I urged Microsoft to stop promoting the broken RSS spec and favor Atom in IE 7 and Vista Feed Engine as the primary choice.
