Justin Wells wrote:
> Quoting Jim Bailey ([EMAIL PROTECTED]):
>
> > Learn JSP and that skill transfers to a dozen or more servlet
> > engines/application servers. Learn WebMacro and you can design using
> > WebMacro. In terms of professional development, I would rather know standard
> > JSP than a little used proprietary solution like WebMacro. Not that learning
> > either one is going to be particularly hard, just that JSP is going to have
> > far wider applicability.
>
> WebMacro isn't proprietary. It's free software, available with full source
> code, under the GNU GPL. In awhile I will be releasing it under an
> additional license on top of the GPL, to make it more accessible to
> commercial users.
(Webster)
Proprietary: one that possesses, owns, or holds exclusive right to something;
You are the copyright holder, and if you were not, you wouldn't be able to
relicense it.
But that's just picking nits.
> But it isn't proprietary. You get the source.
You also get the source for Tomcat/Josper, and under a much freer
license. There's a debate on Slashdot right now about GPL and
dynamic linking. As it stands, if someone wants to sell a servlet
that extends WebMacro and uses templates, their legal standing with
respect to the license is unclear. RMS says that dynamic linking
is covered, which means anything that extends WMServlet must also
be licensed under the GPL.
> What you probably mean is that it is not a Sun backed standard, which
> is different, and also not all that important when you're dealing with
> an opensource application. Or maybe you just meant that there are
> more people using JSP, which is true.
There are many more implementations of JSP also. GNUJSP, PolyJSP, zJSP,
RocketJSP, Caucho, JRun, JCCSP, to name just a few. Most of those
come with the source, and one can pick and choose implementations based
on needs.
That's the benefit of having a *spec*, rather than just an implementation.
> However, people here are making it sound like WebMacro is some big huge
> thick book of learning. It's not. JSP may be all that--but WebMacro is
No, it is you who are insisting that JSP Taglibs require significant
learning vis-a-vis webmacro. All WebMacro does is replace the need
to learn Tags with the need to learn what your senior developer has
placed in the context object, and which properties are available.
I never asserted that WebMacro *syntax* is hard, what I asserted is
that, like any tool, there is more to using it effectively than reading
the instruction booklet.
You keep asserting that WebMacro's simplicity or syntax alone is
enough to justify it's use over JSP. But you're wrong, because the
difference between Webmacro syntax and JSP taglib XML syntax is purely
a matter of aesthetics. You don't like <jsp:.../> or <taglib:.../>,
fine, but that's your preference.
Python uses prefer indentation to indicate blocks rather than {},
Eiffel/Pascal/ADA programmers prefer verbose syntax to C's terse
overloaded syntax. But make no mistake, these are purely aethestic
judgements and no one can prove supremacy of one over the
other. That's why language wars are never won.
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
