Martin Cooper wrote:
This "clutter" is inside the JAR file and loaded on demand when the tags are used. The size of the JAR file could be reduced by pulling these into a separate JAR, but this still doesn't require a "plugin". The idea of the plugin is that something is added rather than removed. I guess I don't see shipping the tags in the core JAR as clutter, even if an application isn't using them. The tags themselves (minus the dojo stuff) don't seem to be all that large.On 10/5/07, Brian Pontarelli <[EMAIL PROTECTED]> wrote:I've brought this up before and in a few bug reports but I think that fundamentally fixing the issues that exist with FreeMarker, the tags and OGNL is more important than ripping them out and allowing pluggability. Also, in my not humble opinion, heading back to JSPs seems like just a step in the wrong direction.Let's say that FreeMarker and OGNL were perfect for everything (I know a stretch, but let's assume), what does removing the tags offer? It reduces some coupling (good). It provides a better managed dependency (both good and bad). Anything else?It allows the people who don't use them to leave the clutter out of their apps. An increasing number of people are building apps in pure DHTML, Flex or AIR, and simply have no need for server-side rendering at all, let alone tag libraries.
I'd definitely be in favor of removing extras, like DOJO in favor of a plugin for these types of components. But I'm not sure I think removing the base tags is the best approach.
-bp
smime.p7s
Description: S/MIME Cryptographic Signature
