Source? (EDIT: Nevermind, I see the GS devs on here mentioning it)
As a project lead at my last job I championed jmvc for a new project. We had mostly good results but there was always a couple developers who were against it (and who IMO worked to undermine it).
We were building a very ajax-heavy UI for an Ad network. Think.. Adwords UI meets MailChimp UI.
In our case, my biggest worry was how easy it is to write spaghetti JS. A classic example is a page with several JS includes and they all are binding to the same event (or to different events on the same element). You're in one file working and you have funny results and you only then discover the event handlers in the other file and then you have to refactor the whole mess. We actually had that a lot in a previous project.
Also, 2 things jmvc did that excited me:
1. Easier JS unit tests.
2. Fixtures! You can build and test the JS without relying on the server to send you the json you need.
As a project lead at my last job I championed jmvc for a new project. We had mostly good results but there was always a couple developers who were against it (and who IMO worked to undermine it).
We were building a very ajax-heavy UI for an Ad network. Think.. Adwords UI meets MailChimp UI.
In our case, my biggest worry was how easy it is to write spaghetti JS. A classic example is a page with several JS includes and they all are binding to the same event (or to different events on the same element). You're in one file working and you have funny results and you only then discover the event handlers in the other file and then you have to refactor the whole mess. We actually had that a lot in a previous project.
Also, 2 things jmvc did that excited me:
1. Easier JS unit tests. 2. Fixtures! You can build and test the JS without relying on the server to send you the json you need.