On Tue, Aug 24, 2010 at 5:55 AM, Johannes Geppert wrote: > Even in the trivial cases a taglib has a benefit. >
*Only* in the trivial cases. > A normal AJAX request with a simple indicator and an effect after > completing, needs a lot of boiler plate code, which is hard to maintenance > and to debug. > There's not much boiler-plate code for that, and as with anything else, you refactor your JavaScript. It's a function call, not embedded in the body in keeping with good practices, etc. And since no two apps are the same, what you need is almost certainly what I need. And I'm not locked in to a specific version of a specific framework. And I could just as easily put *exactly* what I need into my *own* tag library. I can count on one finger the number of times an existing tag library solution worked for me. I see almost zero benefit, except for the most trivial use cases (as long as the tag library uses the JavaScript framework I'm already using and does precisely what I need). I'm not saying don't use them, I'm saying they're not that useful for me and save me very little effort (if any), and occasionally make things *more* work. Dave
