Design Element
Comment on "Separation of Model and View Web Frameworks"
by Scott Stevenson — Aug 03
@Mario Enriquez: Scott, would you please briefly comment the reasons you would like to avoid a java base solution for web development

There are two reasons for me.

The first is that (in my experience) adding a Java virtual machine, a Java compiler, and an app server to the equation introduces a lot of complication and potentially a lot of resource overhead. Java can provide "robustness" that something like PHP can't, but it can also be complete overkill for small or mid-sized apps. Obviously, companies with a dedicated app server staff have an easier time.

Secondly, I don't really like working in the Java environment. I'm not saying the Java approach doesn't have value, it clearly does. Personally, though, I'm used to framing things using dynamic languages and the design concepts in Cocoa. That said, I could be convinced to use the Java language if the frameworks and design patterns were closer to those in Cocoa and Rails.
Back to "Separation of Model and View Web Frameworks"
Design Element

Copyright © Scott Stevenson 2004-2015