Well, the great thing about MyFaces (and somewhat about JSF) is that its open source (and JSF is a somewhat open standard), so if you find great features from other frameworks, there's no reason that they can't be incorporated into MyFaces or JSF. With OS2 vs. Windows, you were left to your own devices, unless you were a really good windows programmer.
Furthermore, you can always stick with your old framework, if you honestly think its better than JSF. JSF is still maturing, and I think it will eventually become a very strong framework. It won't get there without lots of help from early adopters like us, though. We are riding the wave of the future, and to me that is exciting. On Tue, 1 Feb 2005 06:27:02 -0800 (PST), Woodchuck <[EMAIL PROTECTED]> wrote: > yea, i guess this is what it really boils down to: just go with the > flow > > if the flow is going to JSF then i'd better go there too... > > it's not a matter of right or wrong, it's just a matter of progressing > > OS2 was arguably a better OS than Windows, but the flow was with > Windows... > > (but still there is something unsettling about arbitrarily going with > the flow because deep down you like to think you are really making the > right decision because there is no evidence to the contrary... ) > > > --- Martin Marinschek <[EMAIL PROTECTED]> wrote: > > > I believe exactly this plethora of APIs was the reason to invent JSF > > in the first place - to have a common, standardized API that has that > > little edge with respect to the other technologies in place. > > > > JSF may not be the better wheel, being more round than others ;) but > > it is the standardized wheel you will soon be able to plug in in any > > car (=J2EE Server) and use with any tool manufacturer (=Visual IDEs). > > > > You will still have people who don't believe in the standard, but the > > majority of the people will go there where the java community process > > has put its vote - and usually with a base technology like web > > engineering you will want to be there where the most of the action > > is; > > except you have some very good reasons not to do so. > > > > regards, > > > > Martin > > > > > > On Mon, 31 Jan 2005 20:48:23 -0800 (PST), Woodchuck > > <[EMAIL PROTECTED]> wrote: > > > hihi, > > > > > > can we just step back for a moment? > > > > > > if someone was to start a new java web application, he/she would be > > > confronted with (too) many choices. > > > > > > why is there such a plethora of (essentially) APIs? what do i > > mean? > > > > > > this: > > > - tapestry > > > - velocity > > > - jsf > > > - struts > > > - hibernate > > > - cocoon > > > - spring > > > - (add other APIs i left out here) > > > > > > why are there so many choices? this is confusion. this is not > > helping > > > to standardize anything. (at least it certainly doesn't seem to be > > > heading toward that way) > > > > > > is it because everyone thinks they are right? everyone thinks they > > > have the better way to do it so they just make an API? > > > > > > why does everyone want to reinvent the wheel (or add another > > wheel)? > > > > > > why can't we just stop adding wheels, and keep making the same > > wheel, > > > but become very very good at making the same wheel (fine-tune, and > > > polish it in doing so)? it seems we are making new wheels before > > the > > > old wheel gets a chance to roll very much. > > > > > > lol sorry for my analogy, it's what i feel right now about the > > state of > > > java web app development... it's just that there is no time to > > slowly > > > evaluate and keep up with every thing that comes out because i have > > no > > > time to. intial estimates are never enough, scope creeping, > > > requirements change/evolve, but of course deadlines stay the same. > > > it's just a rush to get things done, nevermind designing things > > > ideally/perfectly... and testing other frameworks and APIs and such > > to > > > find the best... > > > > > > you know, the marketing ppl that are selling don't understand > > > technology.. they just want the web app to work like a traditional > > > client/desktop application with all the frills, and when you tell > > them > > > things like cross-browser compatibility issues, performance issues, > > why > > > the browser back button screws things up, etc... they just look at > > you > > > funny without a care because they've already sold the idea to the > > > customer and i have to turn his scary/is-it-even-possible > > design/ideas > > > into reality > > > > > > sorry to digress... but going back to my post, how is it possible > > for > > > anyone to make the best decision when: > > > - not every project has the same requirements (and therefore you > > > cannot know which framework is best until implementation time and > > > discover the pitfalls/benefits) > > > - there is no time to evaluate frameworks/APIs thoroughly (as i > > said, > > > i have no work time.. anything i want to find out is from my own > > > personal time) > > > > > > can anyone out there honestly say their architecture is the best > > > possible choice for their projects (performance / scalability / > > > maintainability)? > > > > > > if not, then is it not apples and oranges? just pick one > > framework, > > > any one will do really. and stick with it. and make the best of > > it. > > > > > > is this (so) bad? is this anyone's reality? > > > > > > > > > woodchuck > > > > > > > > > __________________________________ > > > Do you Yahoo!? > > > Yahoo! Mail - 250MB free storage. Do more. Manage less. > > > http://info.mail.yahoo.com/mail_250 > > > > > > > > __________________________________ > Do you Yahoo!? > Yahoo! Mail - 250MB free storage. Do more. Manage less. > http://info.mail.yahoo.com/mail_250 > -- -Heath Borders-Wing [EMAIL PROTECTED]
