Live data from Hacker News

Ask HN: For the prototype.js users -- is it worth it?

news.ycombinator.com

11–16 of 16 posts

Re: Ask HN: For the prototype.js users -- is it worth it?

#11
post #8

Depends on what are you going to do - I created quite big apps in both jQuery and Prototype. Whatever you want to do - you can do in both - it all depends on the size. I find Prototype better for big projects where you can use it's class system. It feels like Ruby as well. jQuery on the other hand is small and gets the job done, but without a plan on how to structure your code things can get really messy.

I felt this way before until they released their widget framework. It gives you a really good option for writing jQuery friendly javascript throughout your entire app. I don't know if that was the intent, but in terms of fitting an application within the scope of the jQuery framework, the widget features are great.

Re: Ask HN: For the prototype.js users -- is it worth it?

#12
MooTools (http://mootools.net) contains all the capabilities of jQuery and Prototype.js, together with a very impressive class system which allows for better modularity in your code. It has a very supportive community and is being constantly developed. You might also want to read Aaron Newton's long post comparing jQuery to MooTools: http://jqueryvsmootools.com/

That being said, you'll find much more people fluent in jQuery or Prototype.js than in MooTools.

Re: Ask HN: For the prototype.js users -- is it worth it?

#13
post #2

We use it at both the day job and in my business. It is clearly better than nothing. If I were starting from zero today, I'd take a very close look at JQuery, as I think the web development community is rapidly standardizing on JQuery, which means pre-made things that I want to incorporate are disproportionately written in JQuery. However, I have never been totally unable to find a Prototype moral equivalent for the…

Yep, your math is about bang on! :)

Re: Ask HN: For the prototype.js users -- is it worth it?

#14
post #12

MooTools ( http://mootools.net ) contains all the capabilities of jQuery and Prototype.js, together with a very impressive class system which allows for better modularity in your code. It has a very supportive community and is being constantly developed. You might also want to read Aaron Newton's long post comparing jQuery to MooTools: http://jqueryvsmootools.com/ That being said, you'll find much more people fluent…

Yes, Aaron's post is a very good read. I still went with jQuery nonetheless.

Re: Ask HN: For the prototype.js users -- is it worth it?

#15
Love prototype, works around browser issues, is fast and if you really need special effects, get the script.aculo.us companion lib. Other bonuses, it enumerates, and navigating the dom is easy. If you need updating via ajax there is a lean function or full on functions and callbacks it can do that too.

Re: Ask HN: For the prototype.js users -- is it worth it?

#16
post #11
post #8

Depends on what are you going to do - I created quite big apps in both jQuery and Prototype. Whatever you want to do - you can do in both - it all depends on the size. I find Prototype better for big projects where you can use it's class system. It feels like Ruby as well. jQuery on the other hand is small and gets the job done, but without a plan on how to structure your code things can get really messy.

I felt this way before until they released their widget framework. It gives you a really good option for writing jQuery friendly javascript throughout your entire app. I don't know if that was the intent, but in terms of fitting an application within the scope of the jQuery framework, the widget features are great.

Oh, good to know - I haven't looked at jQuery since 1.2 since Prototype and MooTools where doing the job for me.
Post reply on HN