On Thu, Dec 17, 2009 at 12:52 PM, Jim Driscoll <Jim.Driscoll@sun.com> wrote:
While the wicket fanboys like to bang on pots and pans and make a lot of noise, I think it's important for me to say where I think we should really be paying attention -

The following 2 Indeed job trends graphs hopefully make my point:

http://www.indeed.com/jobtrends?q=jsf%2C+gwt%2C+jquery%2C+yui%2C+dojo%2C+wicket&l=

http://www.indeed.com/jobtrends?q=jsf%2C+php%2C+asp%2C+rails%2C+wicket&l=

We can learn a thing or two from wicket, but I'd rather learn from or work with technologies that are actually in the process of breaking out, or have already had great success.

Just something to keep in mind next time you get a derisive tweet.

Jim

P.S.  And that's also a reminder to me that I really need to look at GWT again.  And I still have that action item to examine our interoperability with jQuery more thoroughly.

P.P.S.  Yes, I think jQuery has won the JS framework wars for the time being.  The jobs data backs up my anecdotal experience.  The breakout appears to have started about 2 years ago.

Speaking of jQuery and JavaScript libraries, one question that came up was how does the developer ensure that if he/she is using two different Ajax-based JSF 2 component libraries that use jQuery, for instance, the library is only imported into the page once? Is there any idea of using a registry of common libraries namespaces? This would pertain to @ResourceDependency on a UIComponent in two different component libraries, both referencing jQuery. We have this unification already with javax.faces:jsf.js.

-Dan

--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597

http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://www.google.com/profiles/dan.j.allen