Jupiter Consulting, a development outfit and the creators of the JavaScriptMVC framework, has posted a guide on organizing jQuery applications with JavaScriptMVC 3.0. Justin Meyer, the author of the post, felt that other guides to organizing jQuery applications failed to emphasize a crucial aspect: breaking up applications into separate and testable components. “The secret to building large apps is NEVER build large apps,” Meyer writes. ” Break up your applications into small pieces. Then, assemble those testable, bite-sized pieces into your big application.” Meyer looks at Srchr as an example.

Meyer explorers the way Srchr is organized not as an example of the best way to organize an application, but to illustrate the hows and whys of breaking up applications into smaller pieces.

In another post, Meyer explains the features of JavaScriptMVC. According to the Why JavaScriptMVC page, the framework helps with:

  • 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

JavaScriptMVC has been criticized as “too enterprisey,” but Meyer has also argued that JQuery needs the enterprise.

What do you think? Is JavaScriptMVC a helpful tool for creating large JavaScript applications?