Re: Looking For Direction

On Jun 9, 11:19 pm, "JC"<jjcarde...@hotmail.com> wrote:


In addition to what everyone else said, I'd like to concentrate on
this point. Are you really sure you need a web-based interface (i.e.,
do you really need to expose your application to potentially anyone
anywhere), or are you considering it just because it's today's trend
to build web applications?

In my experience (2+ years in JSF + some minor projects with Struts)
web applications often face an additional layer of complexity than
client-server applications, and are generally limited in functionality
(by the browser and by the stateless nature of the HTTP protocol).

I think JSF especially is a very bad choice. I used the ICEFaces
implementation, which adds its own host of problems, but JSF in
general is terribly complex, and has a fundamentally bad design.
Imagine someone proposed to you, for a client-server application:
"hey, let's do this cool thing, let's keep *all* the GUI state on the
server and ask for it *each and every time* the user interacts with
the GUI"... you would say that's crazy, wouldn't you? Yet it's
precisely what JSF does

                         (and ICEFaces exacerbates the problem by
forcing everything to be AJAX, even stuff that could be client-side
only, like help tooltips).

                      Then, there's the complex and strict life
cycle,

the macroscopic mistakes in the class hierarchy,