If you're looking for someone to tell you which is the best framework, you won't find the answer here, because there isn't one. You have to determine which framework best suits your preferences, your organization, the current development resources/assets and most of all, the requirements.
If you're looking for someone to tell you which you should learn, to get a jump on the next opportunity, the answer is 'all of them.' Of course this isn't realistic because we all have lives and don't care to have 'enrichment' consume our every waking moment, but you could conceivably know *something *about all of them. Add to that, my belief that you don't truly know a framework until you've COMPLETED a project which uses it. I'm reminded of a great Physiology professor I had in college (I was in a Physical Therapy degree program before switching to CS) who, when asked what we needed to know for exams, responded only with "Know everything." On 8/31/06, Elhanan Maayan <[EMAIL PROTECTED]> wrote:
this: http://www.theserverside.com/tt/articles/article.tss?l=JSFTapestry so the question continues with new applications go for struts 1.3 learn webwork 2.2 (webwork in action, or developing web apps with lightweight framework ) and then go to struts 2.0 (struts in ww clothing?) use J.S.F commit suiciide by using shale for production? use tapestry with almost not vendor support? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
