Slashdot Mirror

← Back to Stories (view on slashdot.org)

Going beyond JSP with Ruby and Seaside

Posted by ryuzaki0 on from the whenever-I-stroll-along-with-you dept.

An anonymous reader writes "The Java community has used JavaServer Pages (JSP) technology through most of the last decade, but signs of rust are starting to show. Longstanding conventions inhibit Java programmers from using Java code within Web pages now. Other languages handle Web development much better than Java. This article discuss how code generation works in Ruby, and it delve into a more radical component-based approach in Seaside."

3 of 66 comments (clear)

  1. Re:Flame on! by plopez · · Score: 2, Interesting

    You could say there are signs of nothing but rust on COBOL yet it's still very heavily used in financial applications (back end).

    Wrong! It's no just for the 'backend' these days! And you thought the old farts weren't 'with it'.

    http://www.cobolscript.com/

    --
    putting the 'B' in LGBTQ+
  2. I prefer using Java for web apps, thank you. by master_p · · Score: 2, Interesting

    I prefer to use one environment for my apps. After all, the browser is a glorified 'window system' no different than X-Windows in concept...and the best toolkit for this job right now is Echo2.

  3. Thanks for the laugh by LizardKing · · Score: 3, Interesting

    Longstanding conventions inhibit Java programmers from using Java code within Web pages now.

    That's because you don't want to mix business logic with presentation logic. Any "programmatic" logic you need for presentation can be accomplished with the JSTL, hence most people disable scriptlet support. Only novices would advocate placing code into templates. I shouldn't complain though, as I can rely on these novices fucking things up so much that I can always find work replacing their abominations with something scalable and maintainable.