Win a copy of Murach's Python Programming this week in the Jython/Python forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

My second comeback at JSTL: JSTL AND EL SUCK!  RSS feed

 
Ivan Jouikov
Ranch Hand
Posts: 269
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Here's my reasonsing. Tell me why I am (not) wrong:

After getting convinced to try JSTL, I learned the following things:


  • JSTL and EL are inefficient. Tests on similar pages clearly showed that. (compare - ${name} with <%=name%>, run in a loop 10000 times, you�ll see the difference)
  • JSTL is cumbersome � someone told me once that the reason they use JSTL is because their designers are scared of <%=%> code, but they have no problem throwing around XML statements. Well, what�s my advice to him: hire new designers, and fire your high school students. On one hand, yeah ${parameter.name} is very nice relatively to <%=request.getParameter(�name�)%>. But after playing around with JSTLs u�ll see what I mean. Also, when your designers screwes up with the logical structure of your web-site cuz he thought he could just �throw around� tags, you�ll think twice. Which brings me to the next point�
  • XML is for data flow, not for logic. Whoever the hell thought of tags like <c:if> and <c:choose> should be murdered in the worst way possible. With JSTL�s exporting and importing variables, and all the logical statements and loops, the whole idea of XML gets destroyed.

  • EL encourages sloppy syntax. It doesn�t even have data types (well it has on the bottom level, but not on the surface). Remember JavaScript? Did you know that at first, it was supposed to be server-side scripting language? You know the reason it didn�t make it (one of the major ones)? Because of its sloppy syntax and the amount of errors it caused. Why bring it back?
  • Server-side content and client-side content should be separated. When everything looks like HTML (in some way), it�s hard to tell what actually gets processed, and what gets sent to the client as static (if you have all-nighters, you�ll understand).
  • JSTL is time-consuming. The whole idea of JSTL was to speed up the process. Not only is it less efficient than embedding code the normal way, but it also takes you forever to make something new with it. Don�t believe me? Just try it.
  • The only reason JSTL was made is so that guys at Apache could write some stupid book explaining its hella complicated syntax, and charge people $50 for it. See, it�s just like the C++ story. Why was C++ invented? To give programmers jobs. No other reason whatsoever, C does whatever C++ does just as good, and better. So I am not sure if JSTL is a step to having �advanced� developers who get paid more because they took time to learn retarded JSTL syntax and EL, or is it just Apache�s developers� way of making money (and I am surre O�reilly and the bros are thankful too).


  • Point of this message: DO NOT USE JSTL OR EL. You�ll regret it. I did.
     
    Ivan Jouikov
    Ranch Hand
    Posts: 269
    • Mark post as helpful
    • send pies
    • Quote
    • Report post to moderator
    I just think that most of your arguments are senseless because they don't go to the real matters (and benefits) of using JSTL.

    How bout an example?

    Also, that comment about C and C++ is just absolutely wrong!

    Looks like you haven't been around usenet before C++ was developed.

    I sugest you to keep studying Java, because if you think that "C does whatever C++ does", you have no clue about what you're taking about (at least if we're talking about ANSI stuff).

    And I suggest you get a job where you have to work with 8 other people (4 devs), and write a program in C++. Also, I've worked on a project twice as big in C and Java, with 3 other developers and 2 designers/marketers. We got the job finished in half the time the first project took, and fixing bugs after the project was distributed was a snap.

    I suggest you work in the industry before making such "out of nowhere" statements.
     
    Kyle Brown
    author
    Ranch Hand
    Posts: 3892
    5
    • Mark post as helpful
    • send pies
    • Quote
    • Report post to moderator
    Actually, I have to agree with Ivan. I am familiar with JSTL and EL (we covered them in my latest book, and I've done a few projects with them) and I think it's an abomination. The best I woudl grant is that it may have been based on a good idea (make separation of content logic easier) but that's not what it achieved. As it is, it's a gosh-awful mess.

    Kyle
     
    • Post Reply Bookmark Topic Watch Topic
    • New Topic
    Boost this thread!