So, to carry on the theme from the previous post I've been playing with JSF quite a bit lately. I've recently been moved over to the Architecture team and this team isn't so Java savvy. They do learn quickly they/we are working on a proof of concept application and they opted to do Spring MVC in lieu of Java Server Faces. Mostly do to the very steep learning curve; they wanted to learn something fairly easy to help meet their delivery dates. Since they don't have much of any Java experience it was probably a wise choice.
Except for the fact that the development team that they are supposedly leading doesn't use Spring MVC for anything!!! The dev team is a strict Struts shop until the last project that I did which introduced JSF, which seemed to be a very successful experience, although a rather painful learning curve.
Having said that what exactly does it mean to have a standard if the people that should be defining don't follow it? <- that is mostly just a complaining kind of question I suppose.
My real question is with all of the web frameworks out there (and that isn't even a comprehensive list, especially if you start looking at various JSF Implementations ) how can you ever decide what should be your company's standard? A search of JSF at Dice dot com shows 1,605 jobs Struts has 2,318. I'm sure there is a bit of cross over but that is a significant difference. Supposedly JSF is the direction the industry is moving towards - in fact IBM is not longer actively supporting Struts on their portal servers, so I guess that must mean something.
So why do enterprise development teams set standards if the technology moves so quickly? As soon as you set them they're out of date... So why then?
- Development Speed
- Easily found skill set
- Support Structure
- Long term viability of the technology
I guess that is a decent list - not terribly comprehensive but things to think about when deciding on a standard. What things would you think about? What frameworks are standard where you work?