Why jQuery Needs JavaScriptMVC Part 2

Friday 13 August, 2010 by justinbmeyer

After writing my previous article on Why jQuery Needs JavaScript, I feel like I didn't communicate why JavaScriptMVC is important for jQuery developers.  Here's a much more succinct way of saying it.

JavaScriptMVC makes doing everything you should be doing as easy as possible

Here's some of the things you should be doing:

  • Testing (especially automatic and functional testing)
  • Documenting
  • Breaking up code into logically organized files
  • Compressing and concatenating your JavaScript files
  • Using and organizing client side templates
  • Making plugins that clean themselves up are internally organized, and extendable.
  • Error reporting

All of these things are hard or impossible to do right with jQuery alone.  

You can add your own automated testing library - Selenium or qUnit, qUnit isn't automated. Selenium is hard to write tests for.

You can add your own documentation engine - JSDoc, but make sure you keep track of every file!

You can add your own way of loading and compressing scripts - RequireJS.

You can use other client side template libraries - jquery-tmpl, but you won't be able to compress them into your build or put them in external files as easily.

You can be careful to structure your jQuery plugins so they can be easily removed from an element, remove all event handlers, and provide some mechanism for extending or overwriting your plugin.

You can devise your own way of doing error reporting.

Or

You can download JavaScriptMVC and run:

js steal/generate/app APPNAME

and get all of these things for free.

This is why jQuery needs JavaScriptMVC - to make it easy to do the things you should have been doing in the first place.

We've spent almost 3 years refining the same feature set to make it crazy easy to do these things. If this doesn't make sense to you, please read why JavaScriptMVC is not too Enterprisey.

Subscribe to:

Related Content

Copyright ©2007-2010 Jupiter IT.