There is a fascinating underlying current happening here. I believe
we're in this unique stage where dynamic, ajax-friendly js libraries are
popping up everywhere. It's like a gold rush in a way and at the end of
this stage only a few libraries will make it. It's anybody's guess how
it will all turn out but I would say one of prototype's weakness is how
it plays with others. This is especially true if people starting
putting together cool widgets from various sources.
I would guess that if prototype (and all of its dependant libraries)
could make the switch to not colliding with other libraries then it
could indeed have a better shot at being the king library. Fueled by
Rails growth and the nice widget libraries like ours here, prototype has
a definite edge but if other non-Ruby frameworks opt for other libraries
then its potential will be hindered. It's also just a matter of time
until other widgets are ported to the 'other' libraries.
I don't even know if Sam and Thomas would even consider such a change as
that would most likely break a ton of existing code which may be a deal
breaker.
As for Martin's issue specifically, Apache MyFaces is a big project that
will be used by the Java community. They are not a single application
solution, Java web projects everywhere will consider using MyFaces only
if it plays nice with their current application. So the MyFaces
project, correct me if I'm wrong, has to be very careful in what
technologies it bundles. Though given the component nature of JSF
having a strong widget library is just huge.
Cheers,
Marty
_______________________________________________
Rails-spinoffs mailing list
[email protected]
http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
