For me, it's all about the right tool for the job. 3 for corporate use, 2/5 for personal use. Corporate dev usually needs easy-peasy least common denominator-type tools, and JSP certainly fits the bill. It's easy enough for almost anyone to pick up and is theoretically possible to keep maintained if some guidelines are followed, but too often I've seen 1000+ line JSP pages and pages with a lot of c:ifs that blow out the 64k class file limit (!!).
For personal use, it's like PHP, great for popping up some quick-n- dirty pages, hence the 2. When your app gets to more than 3-5 pages you probably need to look at some framework, and there's so many good choices out there not based on JSP. On Apr 8, 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]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
