Excuses to not advocate web framework X
Alright fanboys, we know that you love your web framework and wishing others would see it the way you do. So you’re wondering why people don’t want to use your framework? Here’s my excuses:
- Seam: JSF ’nuff said….immediate=true anyone?
- Struts2: 5 years of Struts1 horror and you expect me to continue to follow the Struts tradition?
- WebWork2 (re-branded to Struts2): i have to implement some interface for my Action?
- Stripes: see WebWork2
- Wicket: hmmm I have to learn Swing again?
- Grails: why is my IDE-refactor broken??
- Tapestry5: 4 versions, so this is the groundbreaking release?
- Spring-MVC: sure when XML is cool again
- Vanilla Servlet+JSP: are you kidding me?
October 16th, 2007 at 9:59 am
I guess my question is…Do you just not do Java Web Development? You’ve knocked out most of the major players. Ah, maybe you’ve rolled your own?
October 16th, 2007 at 10:32 am
I’m also curious what you use then. It’s easy to sit on your couch and bash every major framework. How about something of benefit and making a suggestion?
Are you still using Servlets?
out.println(”Regards”);
October 16th, 2007 at 2:02 pm
Oh yeah–I do Java web development, and I use whatever framework that’s agreed upon from the start of the project. Or if the decision was mine, then I have my favourites, and you probably have one or few as well.
To be fair to the other frameworks, I have to “tease” (not bash) every one of them even including the one I enjoy working with the most presently. The point is no matter which framework you think is the “greatest”, there’s always going to be ‘fanboys’ of other frameworks that’s praising them and riding them as hard as you do with your own choice.
What I find interesting is that there always seems to be an excuse(prejudice maybe?) for not wanting to believe that there maybe something else better. I’m just merely stating the obvious.
October 19th, 2007 at 3:12 pm
My only response to the JSF comment, and this is by no means to defend this horrible problem in JSF, is that the default life cycle should have had Ajax incorporated from day one. The immediate=true problem is a workaround in a non Ajax world. With Ajax4jsf (now RichFaces) available, it truly makes JSF live up to its purpose. I will let you judge if that purpose is a good one, but at least it works now how it was designed. Of course, we need to get this into the standard or else it is hard to call it JSF, but hopefully with Gavin (and Seam folks) working with the JSF team, things will happen.