From: Anjo K. <kr...@lo...> - 2006-08-24 20:28:29
|
Am 24.08.2006 um 22:12 schrieb Jean-Fran=E7ois Veillette: > This would avoid the ajax framework to be a wo-wrapper on top of a > single js library. > This would let the framework be open to new feature and libraries in a > structured way. Actually, this is the worst of all worlds. Firstly, the packaging =20 doesn't help unless you also use packages in your wod which I totally =20= hate. Then you need to support and test all these components, wrap =20 your own head around both libs, you'd spread resources over these and =20= for what gain? So that *someone* at *some* time comes and says "eh, =20 can't we use this in mochikit" which is the one thing you don't support? No thanks. I am so totally sick of this tendency that java =20 programmers seem to have, "flexibility" when it comes to frameworks. =20 Heck, we are using WebObjects! Probably the only app server left that =20= is not modelled after some standard! Nope. If the stuff works =20 together, fine, we may leave it as it is, but no more new libs. If it =20= doesn't we use one thing only unless there is a total must have. And anyway, have you ever looked at the scriptacolous code? function $$() { return $A(arguments).map(function(expression) { return expression.strip().split(/\s+/).inject([null], function=20 (results, expr) { var selector =3D new Selector(expr); return results.map(selector.findElements.bind(selector)).flatten=20= (); }); }).flatten(); } Wanna guess what this little gem does? No peeking in the docs! Cheers, Anjo |