I know Ted wants me to quote him and respond for a bit of fun…. but I will keep it a little short on this one.
1. JSF vs. Rails
I didn’t mean to imply that these are the two choices. The point was to show the extremes of: full component UI model that hides the webness (JSF) vs. very simple wrapper (Servlets).
For some time many frameworks have been going to the JSF extreme, and Rails has come along to give a great balance.
Hacking away at JSPs, or PHP files just becomes a mess quickly. We all learned that. Then we started working with simple MVC things which was fine, and it got complicated.
Rails is rebalancing things!!!
2. Servlets is what you want
Come on dood. You really think that you would want to build a web application in pure Servlets? You will end up following the same path:
- Hmm, my designers don’t want to do out.println(). that gets REAL old
- Hmm, there is more HTML than code here, what can we do about that? I know I will create a templating language to call out too
Servlets are fine for some things don’t get me wrong…. but when I think about developing a web application, I don’t want to start with out.println() as my favourite friend :)