Quoting Craig R. McClanahan ([EMAIL PROTECTED]):
> * If I like the WebMacro syntax, but don't like the implementation (say,
> it might be too slow for my particular app), what do I do?
Find out what makes it slow and fix it? That's what's great about OSS
projects. Or maybe you won't want to do that, but someone else will do
it instead.
> I suppose
> I can go write my own implementation, but of course I can do that with
> the JSP syntax as well.
However, that's a huge amount of work. It's better to take an existing
code base and improve it, then start all over from scratch.
> * If I need to hire a developer and I key "WebMacro" and "JSP" keywords
> into a resume web site, how many hits am I going to get on each?
If you hire a developer who can't figure out how to use WebMacro in a day,
then either you hired the wrong person, or I'm doing something wrong. I
am assuming you hired someone who can write Java code. Ditto for the
templates, except instead of someone who wrote Java code, look for
anyone who has ever written any kind of dynamic web page.
The key to WebMacro is that you do all of your complicated work in
ordinary Java, so all you have to do is hire ordinary Java programmers.
I'm willing to bet there are more of those around than there are people
using JSP.
It's things like JSP where you might have to worry whether your hire
has previous experience or not, because it builds a new architecture
that limits the value of ordinary Java experience. WebMacro doesn't
do that.
You write a normal "mainstream" Java servlet, using ordinary mainstream
Java code. Not weird JSP special-tag stuff, etc.
Justin
===========================================================================
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
