ansaurus

Question

Which one is better framework for Enterprise level JS programming - jQuery or Prototype and why?

Answer 1

+3 A:

Strictly from a long term support and momentum perspective: Major vendors such as Microsoft, Google, Dell, Wordpress, Nokia, etc. have adopted jQuery. Take from this what you may when considering if its Enterprise-ready.

Beyond this, consider that it is likely the fastest growing framework and has a huge following. These two facts should drive it forward with continual improvements and support. Even long term human resource support to develop in it should be there given the number of jQuery developers out there...

KP 2010-02-10 19:21:40

Thanks! I do think both libraries can do all of the above. But which is better in comparison? The bigger following or plugin support are not as important in this case.

JONYC 2010-02-10 19:59:06

Feature specific comparison: http://en.wikipedia.org/wiki/Comparison_of_JavaScript_frameworks

KP 2010-02-10 20:07:13

@JONYC Can you elaborate on your enterprise level project? It's pretty tough for anyone to tell you exactly which one is 'better' as they both suit certain uses.. especially if following or plugin support is not important (which I personally think would be for large scale systems)..

KP 2010-02-10 20:29:37

It's not for a particular project. We wanna choose a framework that is solid (code-wise), extensible and relevant for *years* to come. That's why plugin support isn't much of a concern because they come and go. But I need a good code-base and architecture will allow programmers to do whatever comes up in the future.

JONYC 2010-02-10 20:36:48

In that case I'd definitely recommend jQuery. Major corporations would not adopt a framework that is going to die next year. The big boom in javascript frameworks is jQuery without a doubt. It's easy, has good performance (maybe not the best but still very good) and will be around for a long time.

KP 2010-02-10 20:49:05

Answer 2

+6 A:

Hmm. From an enterprise point of view, I'd have a completely different set.

Expected lifetime of the library;
Learnability;
Availability of programmers;
Integration possibilities;
Quality of plug-in code.

I'd also take a good look at where and how javascript is expected to be used in the company, and how that is going to change.

And in an enterprise setting, you should present this as part of a Technology Roadmap. In that, you take a look at the long time customer needs, how they should reflect in technology developments and choices.

Stephan Eggermont 2010-02-10 19:42:45

Thanks. Your answer is very insightful.. Your points are very good. Assuming this framework is to withstand the test of time and it should be scalable to do anything (from complex animation to multi-threading ajax). What's your take on jQuery and prototype, or maybe another library.

JONYC 2010-02-10 19:56:00

Well, I'm not looking from an enterprise point of view. I am switching from Scriptaculous to jQuery+RaphaelJS. But I'm agile, and can switch to something else when needed (Clamato?)

Stephan Eggermont 2010-02-10 20:11:28

I like this answer better than mine.. very good criteria (which I think jQuery meets all just fine)...

KP 2010-02-10 20:30:36

Envy! We are definitely not agile. Why did you switched? What's your after-thought?

JONYC 2010-02-10 20:30:37

I'm using technology that makes it possible for me to make a difference, in a small group of developers. That means Pharo Smalltalk and Seaside, on a Gemstone object database. The lead developers of Seaside moved to jQuery for new development. My existing code is well-refactored, so switching is no big deal.

Stephan Eggermont 2010-02-10 20:59:33

Answer 3

A:

$().launch_photon_torpedos()

Paul D. Waite 2010-02-10 19:54:44

`$('#trollingAnswer').each(function() { $.TrollTools.ResistUrgeToComment($(this), false) });`

KP 2010-02-10 20:18:09

I make no apologies for making fun of vague laundry-list requirements that unthinking MBA dinosaurs put together to give the illusion of having work to do, and sum up with that most self-important term, “enterprise”. As if proper, big, important companies have proper, big, important needs that could only possibly be satisfied by one particular mature JavaScript framework, as opposed to another particular mature JavaScript framework. If you think “Enterprise level JS programming” actually means anything, maybe you should leave the programming to actual programmers. That said, good answers.

Paul D. Waite 2010-02-11 08:48:31

+1, funny. That should get make a nice zero for your rep. We should leave it at that.

David Schmitt 2010-02-12 14:12:54

Aw, thank you! I should really now write a photon torpedos plugin for jQuery.

Paul D. Waite 2010-02-12 15:27:36

ansaurus

tags:

views:

answers:

Which one is better framework for Enterprise level JS programming - jQuery or Prototype and why?

related questions