I epined on If choosing the web framework is a big problem, think yourself lucky.
I know many people will disagree with me. Especially those that write web frameworks ;)
But:
f you think that the hardest part of the project will be the web piece, and hence you end up arguing about framework A versus B until both sides are blue in the face, I would consider yourself very lucky. At the end of the day, the web side is pretty easy with any of the modern frameworks. You will be able to get the job done in admirable style no matter what you choose. After all, what are these frameworks doing? They are hiding the stateless web architecture and letting you display info in HTML, and push back posted data to a datastore.
Compare that problem to the application which has a really tough algorythm? I am currently working on a project which has a need for near-AI on the server side. An agent will be watching what a user is doing as they traverse the web site. It will be collecting data from the user (based on input, and via what the user does) and then has to go through a set of complicated business rules to give a smart response. Are we spending time worrying about which opensource web framework to use? No. We are focused on the complicated business logic.
February 9th, 2005 at 8:03 am
Great little article Dion.
It’s about time someone steps up and says it’s not THAT big a deal what web framework you choose.
Aslak
February 9th, 2005 at 8:03 am
Great little article Dion.
It’s about time someone steps up and says it’s not THAT big a deal what web framework you choose.
Aslak
February 9th, 2005 at 8:23 am
It depends on where the complexity of your app is. If you have to support multiple types of devices (web browsers, plus wml *and* XHTML phones, with all of the inconsistencies of presentation between different phones), plus rebrand it depending on where the user is coming from (i.e. which mobile network operator), then picking the wrong web framework can make your life hell.
If your UI requirements are straightforward, i.e. you only need to deal with typical web browsers, then I agree most mature frameworks will be able to do the job.
February 9th, 2005 at 8:23 am
It depends on where the complexity of your app is. If you have to support multiple types of devices (web browsers, plus wml *and* XHTML phones, with all of the inconsistencies of presentation between different phones), plus rebrand it depending on where the user is coming from (i.e. which mobile network operator), then picking the wrong web framework can make your life hell.
If your UI requirements are straightforward, i.e. you only need to deal with typical web browsers, then I agree most mature frameworks will be able to do the job.
February 9th, 2005 at 6:26 pm
Well Kief, sometimes that kind of APP has so many differences between one medium and the other that you will just have to accept that no framework will automagically solve that for you. You will just have to put the common bits (Business Logic?) on one side and duplicate the whole frontend work…
February 9th, 2005 at 6:26 pm
Well Kief, sometimes that kind of APP has so many differences between one medium and the other that you will just have to accept that no framework will automagically solve that for you. You will just have to put the common bits (Business Logic?) on one side and duplicate the whole frontend work…