+1 from me for Derrells point of view.
Especially using qooxdoo together with other js frameworks may lead to
problems if those frameworks are implementing polyfills which do not
have the implementation qooxdoo is assuming.
What about all those graphing contribs written by Tobias Oetiker and
ckeditor integration? As they probably all load libs and frameworks
before qooxdoo they probably break qooxdoo itself.
Regards.
Dietrich.
Am 24.07.2012 15:42, schrieb Derrell Lipman:
On Tue, Jul 24, 2012 at 9:30 AM, thron7 <[email protected]
<mailto:[email protected]>> wrote:
You're probably right in that it could be hard to cover the spec
100% with a polyfill. But then, most vendor implementations don't,
so the aim might be to have a "good enough" implementation, no?!
So what is your argument here?! Not to provide polyfills at all?
Not polyfil Function.bind()? Or just caution against making "100%"
the threshold for implementing them?
I'm on the fence. In the past I have argued vehemently against
modifying the prototype of native objects. An early claim of qooxdoo
was that it would never alter native prototypes, yet there were cases
where it in fact did so. In some browsers (IE), functions bound to
native objects would be iterated in a for..in loop, causing the
programmer to have to check for hasOwnProperty() and such, making the
programmer's job harder, not easier.
These days, I'm more inclined towards the concept of polyfills. The
browsers have gotten better, and any browser that people should
actually be using these days probably already supports all of these
features that would be polyfilled. The problem comes when one library
creates a polyfill that does not strictly meet the spec, and some
other library needs one of the features that's not implemented in the
polyfill, but assumes that if the function is available, then it is
fully implemented. We (qooxdoo developers) seem to be doing more and
more incorporating of external libraries in our qooxdoo apps, and I do
worry that we're going to encounter compatibility issues with one
vendor's polyfill implementation or another's.
I think that my opinion is that if the polyfill can be implemented
100% to the spec, there should be no problem doing it. If it can't be
done 100% to the spec, it's probably better left without the polyfill.
Derrell
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
