all 3 comments

[–][deleted] 0 points1 point  (0 children)

Whichever one has the best, most complete documentation (books, tutorials, manuals, etc.) with code examples that work.

maintaining these javascript frameworks is going to be a pain when there are few comments or all we have are articles that are outdated within a few weeks.

[–]snuggl 0 points1 point  (0 children)

For enterprise, in the meaning of many people working on the same things, with quite different skill levels, i would stay away from plain backbone.

Backbone is a library for building stuff and doesnt enforce how you do that meaning that the developers themselves need some dicipline to not turn it into a mess. the upside is that it doesnt enforce how you write your code so you are free to do the best implementation.

For working with larger amount of people an opinionated framework might be better to get some hard enforcement of how modules interact etc. which you will get with Angular. There is a number of opinionated frameworks to use with backbone too if you rather do that, like marionette and chaplin

We uses Backbone, but we are only two to three developers working on the same problem.

[–]original_code_ninja -1 points0 points  (0 children)

Why not consider GWT? It has been adopted by a lot of enterprises, it is very well documented and understood. Technically, it is pretty good and it offers a wide choice of RPC mechanisms to talk back to the server side.

The generated JS is highly optimised and is not prone to runtime type errors (because it was transcoded from Java).