I think it depends on the context for me.
In terms of enterprise development, my day-job, I would say 3. By itself
(standard taglib), it doesn't provide even the basic support for expected
(in our modern days of frameworks) capabilities...foremost on my mind page
templates, workflows, etc. That said, JSP provides extensibility (ie
taglib) that can make it so much more. Isn't that where JSF emerged from
(at least in part), along with some lifecycle listeners and the like? So, I
give it a 3 because I see it's purpose, I don't use it in this context, and
so it doesn't bother me. When I need to bust out a prototype or trivial
app, I still don't say "great, an opportunity for my to demonstrate my
expert command of JSP!", but I have found myself hacking something together
quickly just to prove something while waiting for the pizza to be delivered
(30min or less!).
In the context of a consultant, my off-duty job, I would say 4/5. First,
JSP is a server page (similar to PHP, ASP, etc) syntax. It's easy to learn
and read to those that are starting out. Because the learning curve is less
(easier for previous PHP developers to pickup than full-blown EE
architecture, for example), it can be a good solution for trivial apps
(simple CRUD websites) if implemented properly...but implementation is
usually not done with much foresight because I'm coming behind a developer
that either didn't know, didn't care, or just wanted out. So...I hate
having to maintain/fix inline JDBC calls within JSP, copy/pasted code, etc.
JSP, by itself, provide for so much capability but doesn't enforce
programmatic discipline...so it's often a case of "developers gone wild".
Fortunately, I don't encounter much JSP in consultancy for ecommerce and
similar sites (goes with another thread and the last podcast). I personally
believe this is because it's not supported very well by shared hosting sites
and therefore never had as much of an uptake - so there isn't as many
developers out there, so there aren't many hosts that provide it - and the
cycle continues.
The the context of a trainer, where I find myself at times, I would said 2.
When I need to teach existing web developers (say PHP, ASP, even mod_perl)
Java EE technologies...it's good to start with showing them something
familiar ("See...it's not that scary....now eat these 500 acronyms that is
EE"). JSP is one of those technologies that just works. Coupled with
servlets, you can pretty much do anything you need by leveraging POJO
libraries and utilities in a relatively clean way while allowing you to
start teaching MVC principles without overwhelming newbies. In part of a
graduated, structured, learning curve, I think it's great.
Finally, in the context of potential...I think a 2. JSP provides something
to build on. If you don't like JSF (which I didn't have much love for
before v2), you can do something else. I wouldn't want to see it become a
deprecated or anything like that =)
Regards,
Steve
On Thu, Apr 8, 2010 at 5:25 AM, Moandji Ezana <[email protected]> wrote:
> Last night I was ranting endlessly about how much JSP sucks to another
> developer I'd just met, but she seemed to find it an OK technology. I'm
> wondering if I'm alone in my near-limitless distaste for JSP.
>
> Poll options:
>
> 1. I love JSP.
> 2. I like JSP.
> 3. I neither like nor dislike JSP.
> 4. I dislike JSP.
> 5. I hate JSP.
>
> I'm curious about anyone would choose any of the first 3 options... ;)
>
> Moandji
>
> --
> You received this message because you are subscribed to the Google Groups
> "The Java Posse" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected]<javaposse%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/javaposse?hl=en.
>
--
You received this message because you are subscribed to the Google Groups "The
Java Posse" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/javaposse?hl=en.
