Comments on: Why I often prefer Prototype too http://almaer.com/blog/why-i-often-prefer-prototype-too blogging about life, the universe, and everything tech Sat, 08 Sep 2012 07:06:53 -0700 http://wordpress.org/?v=2.8.4 hourly 1 By: Bryan J Swift http://almaer.com/blog/why-i-often-prefer-prototype-too/comment-page-1#comment-40294 Bryan J Swift Sat, 24 Jan 2009 06:43:47 +0000 http://almaer.com/blog/?p=2241#comment-40294 @Patrick it's a little weird for me to defend jQuery but not only is Microsoft's association with jQuery recent but they are not the controlling interest in the project. Regarding the content of the actual post, I've arrived at a pretty similar conclusion except with MooTools substituted for Prototype. Maybe it has something to do with my Java and classical inheritance background but writing MooTools code just feels right. However, I have definitely learned to apply JavaScript libraries as required by the task at hand and not just to have them. Also, thanks for the cauldron of awesome that is Ajaxian. @Patrick it’s a little weird for me to defend jQuery but not only is Microsoft’s association with jQuery recent but they are not the controlling interest in the project.

Regarding the content of the actual post, I’ve arrived at a pretty similar conclusion except with MooTools substituted for Prototype. Maybe it has something to do with my Java and classical inheritance background but writing MooTools code just feels right. However, I have definitely learned to apply JavaScript libraries as required by the task at hand and not just to have them.

Also, thanks for the cauldron of awesome that is Ajaxian.

]]> By: Joe Chung http://almaer.com/blog/why-i-often-prefer-prototype-too/comment-page-1#comment-40290 Joe Chung Fri, 23 Jan 2009 10:05:47 +0000 http://almaer.com/blog/?p=2241#comment-40290 Try being open-minded, Patrick. Lots of people are using jQuery, not just Microsoft. Try being open-minded, Patrick. Lots of people are using jQuery, not just Microsoft.

]]> By: Patrick Wallace http://almaer.com/blog/why-i-often-prefer-prototype-too/comment-page-1#comment-40287 Patrick Wallace Thu, 22 Jan 2009 23:27:34 +0000 http://almaer.com/blog/?p=2241#comment-40287 I am shocked and surprised that anyone would care what Microsoft is supporting. In fact, from my perspective, that means that JQuery has to be difficult to use because the underlying Microsoftian philosophy is that you are an idiot and we have to hold your hands every step of the way lest you fall and bump your nose. When I hear Microsoft, I turn and go the other way. I am shocked and surprised that anyone would care what Microsoft is supporting. In fact, from my perspective, that means that JQuery has to be difficult to use because the underlying Microsoftian philosophy is that you are an idiot and we have to hold your hands every step of the way lest you fall and bump your nose. When I hear Microsoft, I turn and go the other way.

]]> By: Rey Bango http://almaer.com/blog/why-i-often-prefer-prototype-too/comment-page-1#comment-40281 Rey Bango Wed, 21 Jan 2009 23:31:38 +0000 http://almaer.com/blog/?p=2241#comment-40281 @Nicolas: In some cases you're right. Luckily, we've had a ton of success in attracting extremely sharp people to the jQuery community. In addition to that, we have one of the most supportive and accepting communities around. We're more than willing to work with people that may just be starting out in their client-side experience and help them through many of the hurdles found in JS development. The same can't be said for all frameworks, which adds to the attraction of the jQuery project. @sean: The fact that there are lib choices is a good thing as it allows developers to use the best tools for their specific needs. One of the things that we've really pushed within the jQuery project is ensuring that we play nice with other libs and we've worked closely with the Prototype team to make sure of this. We realize that jQuery doesn't fit the bill for all developers and it's important for us to not impede a developer's need to use another lib. Rey - jQuery Project @Nicolas: In some cases you’re right. Luckily, we’ve had a ton of success in attracting extremely sharp people to the jQuery community. In addition to that, we have one of the most supportive and accepting communities around. We’re more than willing to work with people that may just be starting out in their client-side experience and help them through many of the hurdles found in JS development. The same can’t be said for all frameworks, which adds to the attraction of the jQuery project.

@sean: The fact that there are lib choices is a good thing as it allows developers to use the best tools for their specific needs. One of the things that we’ve really pushed within the jQuery project is ensuring that we play nice with other libs and we’ve worked closely with the Prototype team to make sure of this. We realize that jQuery doesn’t fit the bill for all developers and it’s important for us to not impede a developer’s need to use another lib.

Rey – jQuery Project

]]> By: sean green http://almaer.com/blog/why-i-often-prefer-prototype-too/comment-page-1#comment-40277 sean green Wed, 21 Jan 2009 09:27:59 +0000 http://almaer.com/blog/?p=2241#comment-40277 Well summed up, I totally agree. But with the support and momentum behind jQuery how can you recommend Prototype for a new project? Well summed up, I totally agree. But with the support and momentum behind jQuery how can you recommend Prototype for a new project?

]]> By: jamieorc http://almaer.com/blog/why-i-often-prefer-prototype-too/comment-page-1#comment-40273 jamieorc Wed, 21 Jan 2009 01:06:09 +0000 http://almaer.com/blog/?p=2241#comment-40273 I was thinking recently about Prototype and jQuery. My impression is this: Prototype is heavily object-centric, so when you're dealing with objects themselves, it has wonderful methods available. jQuery is DOM-centric, so dealing with the DOM is a breeze in jQuery. Now, let's get Prototype's methods into jQuery and we'll have a perfect world. ;-) I was thinking recently about Prototype and jQuery. My impression is this: Prototype is heavily object-centric, so when you’re dealing with objects themselves, it has wonderful methods available. jQuery is DOM-centric, so dealing with the DOM is a breeze in jQuery. Now, let’s get Prototype’s methods into jQuery and we’ll have a perfect world. ;-)

]]> By: Nicolas http://almaer.com/blog/why-i-often-prefer-prototype-too/comment-page-1#comment-40272 Nicolas Tue, 20 Jan 2009 21:59:37 +0000 http://almaer.com/blog/?p=2241#comment-40272 Sometimes a big community isn't that good. In a big community you'll have the advantage of beeing able to find more plugins and extensions and stuff like that, that's for sure, but I doubt that the quality of those extensions will always be that good. I like small communities of "clever" people. For example, the Mootools community isn't very big, but the Core and More builds of their framework are very carefully coded, with elegant and readable code. They have an excelent balance between imperative, OO and functional programming paradigms. They have a well thought Class object, that allows extension and implementation (something like multiple-inheritance). A good OO design (Fx.Base, Fx.CSS, etc). Very handy utility functions ($extend, $H, $merge, $empty, $lambda, etc). And a modular code (you can make your own build). Anyway, that's the library I feel most comfortable with. Sometimes a big community isn’t that good.
In a big community you’ll have the advantage of beeing able to find more plugins and extensions and stuff like that, that’s for sure, but I doubt that the quality of those extensions will always be that good.
I like small communities of “clever” people.
For example, the Mootools community isn’t very big, but the Core and More builds of their framework are very carefully coded, with elegant and readable code.
They have an excelent balance between imperative, OO and functional programming paradigms.
They have a well thought Class object, that allows extension and implementation (something like multiple-inheritance).
A good OO design (Fx.Base, Fx.CSS, etc).
Very handy utility functions ($extend, $H, $merge, $empty, $lambda, etc).
And a modular code (you can make your own build).

Anyway, that’s the library I feel most comfortable with.

]]> By: James MacFarlane http://almaer.com/blog/why-i-often-prefer-prototype-too/comment-page-1#comment-40271 James MacFarlane Tue, 20 Jan 2009 21:39:43 +0000 http://almaer.com/blog/?p=2241#comment-40271 I agree with Dion's path of discovery regarding Prototype. There are a lot of handy tools packed in there and there are always more tidbits to find. It has saved me countless hours of work. Sadly, I think Prototype is losing the popularity battle. For example, over at StackOverflow.com, there are over 1000 jQuery posts, and under 100 for Prototype. While I, and others, continue with our efforts to nurture the Prototype user community, having someone like MS jump on the jQuery bandwagon sways a lot of developers in that direction. Prototype's early success really helped move the technology forward. What is needed now is someone big to bolster Prototype's position in the marketplace. I agree with Dion’s path of discovery regarding Prototype. There are a lot of handy tools packed in there and there are always more tidbits to find. It has saved me countless hours of work.

Sadly, I think Prototype is losing the popularity battle. For example, over at StackOverflow.com, there are over 1000 jQuery posts, and under 100 for Prototype. While I, and others, continue with our efforts to nurture the Prototype user community, having someone like MS jump on the jQuery bandwagon sways a lot of developers in that direction.

Prototype’s early success really helped move the technology forward. What is needed now is someone big to bolster Prototype’s position in the marketplace.

]]> By: Adam http://almaer.com/blog/why-i-often-prefer-prototype-too/comment-page-1#comment-40270 Adam Tue, 20 Jan 2009 20:51:43 +0000 http://almaer.com/blog/?p=2241#comment-40270 If Prototype didn't try to impose Ruby programming paradigms on JavaScript, it would be fine. To me it does the same thing as if I had something that let me write my ruby programs using ObjectiveC. If Prototype didn’t try to impose Ruby programming paradigms on JavaScript, it would be fine. To me it does the same thing as if I had something that let me write my ruby programs using ObjectiveC.

]]>