Why Picking Technology is Hard
I think choosing a framework is hard because no framework is perfect. Every framework under consideration is like a Porsche with a gaping hole in the side that just ruins it. The very act of choosing a framework means that you are knowingly accepting every little ugly wart and blemish of that framework, and explicitly saying “Yes, I want to deal with that problem everyday for the next few months!”. We aren’t built to choose things that are going to cause problems for ourselves.
It’s one of the reasons I always revisit the state of web frameworks now and again to see what pain points have been cleared up and what new ones have been created.
One thought on “Why Picking Technology is Hard”
I think this is a big problem because it requires web developers to constantly re-evaluate technologies.
I’ve heard some argue that it’s great that there is so much competition for web technologies because it drives innovation.
Maybe it is necessary? The problem though it is takes a huge amount of time to continually evaluate and re-evaluate web technology choices.
Should I use Java, PHP, .Net, etc?
Should I use JSF, Wicket, etc?
Should I use PrimeFaces, RichFaces, IceFaces, ADF Faces, OpenFaces, etc?
Should I use EJB 3.1, Spring, etc?
Should I use Hibernate, EclipseLink, TopLink, OpenJPA, etc.
Comments are closed.