Though a newbie to prototype working with is not a problem once i
understood the concept the methods of intrest at this point. One point
to note, prototype examples available are mostly rubyonrails based
jQuery on the other hand is php biased. Watched a friend of mine work
with Yui & before he got what he wanted took him a whole day coz what
he wanted was not provided for in the framework so we ended up
introducing prototype into the project the was so happy he started
over the project with proto only.
In short prototype needs more examples in other languages not just
ruby though ruby have prototype as part of the application

On 9/27/08, Nick Stakenburg <[EMAIL PROTECTED]> wrote:
> Andrew, great to hear is coming soon, I'm sure 1.6.1 is going
> to be great. There are great ideas floating around for it, although I
> hope that by the time 1.6.1 is released it won't be seen as Prototype
> playing catch-up. Maybe that's unavoidable though with funded
> frameworks around the corner.
> I just hope the website will get an update as well so it doesn't hold
> people back while the code is only getting better. The code is not
> what worries me, it's the community not paying enough attention. As
> far as I'm concerned getting the community involved is the area where
> other frameworks are outcompeting Prototype at the moment. Looking at
> job openings these days it saddens me to see people having settled on
> some other framework before they even have a Javascript guy on board,
> there you have some competition between frameworks Prototype could end
> up stronger in. I'm not that great on things that don't involve code
> but I'll be looking forward to contributing wherever I can.
> Regards,
> Nick
> On 26 sep, 23:58, Andrew Dupont <[EMAIL PROTECTED]> wrote:
>> On Sep 26, 10:30 am, Nick Stakenburg <[EMAIL PROTECTED]> wrote:
>> > I'm not sure if Prototype has a real future, at the moment it seems to
>> > be getting more and more a side project for it's authors. The reason
>> > jQuery is so popular is it's community
>> The last few months have been unusual for Prototype Core: most of us
>> have been especially busy in our day jobs. Prototype has always been a
>> side project, but then most open source projects are; JQuery is in the
>> enviable position of having its full-time development fully funded
>> (Paul Bakaus's employer pays him to work on jQuery).
>> > What would help is if Prototype focussed more on the community, things
>> > like need to be intergrated into .
>> > People tend to go with jQuery because all they want is plugins, jQuery
>> > has them right there on the main page, while for prototype hardly
>> > anyone knows how to find a plugin so the choice for the average guy to
>> > pick a framework then becomes very easy.
>> In truth, I'd agree with most of the suggestions on how we could
>> improve our community. We're not lacking in initiative; we're lacking
>> in time, and if anyone reading this considers himself/herself good at
>> managing mailing lists, evangelizing, organizing documentation, and
>> the like, we'd love to have your help.
>> In other words, Prototype won't be like MochiKit, which languished
>> because its author lost interest. We just need to find more people
>> that are (a) willing to help out in ways that don't involve writing
>> code; and (b) able to get stuff done. We've got plenty of A, but not
>> much of B, mostly because the people who want to help out are often
>> just as busy as we are.
>> > Perhaps 1.6.1 will breath some new life into things, or maybe not.
>> Nick, I take your opinion very seriously, and it unsettles me to know
>> you're this pessimistic about the future of Prototype. It means we
>> haven't been doing our jobs well lately. We're going to push out
>> as soon as we can and then start focusing on 1.6.1 (which I
>> guarantee will have some stuff you'll love).
>> Cheers,
>> Andrew
> >

Sent from Gmail for mobile |

You received this message because you are subscribed to the Google Groups 
"Prototype &" group.
To post to this group, send email to
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at

Reply via email to