Not sure if I'll ever use it, but intercooler.js would be great for many use cases (that usually end up being implemented using a hugely complicated stack).
The only reason I probably wouldn't use it is that I'm happy with just using browser APIs directly for the small stuff.
I'll just say that the examples make intercooler.js seem much more complicated than it is, until you read closely enough to realize that most of the code is Mockjax and backend implementation. You'd do well to split the view into two parts: frontend source code and server-side source code.
The only reason I probably wouldn't use it is that I'm happy with just using browser APIs directly for the small stuff.
I'll just say that the examples make intercooler.js seem much more complicated than it is, until you read closely enough to realize that most of the code is Mockjax and backend implementation. You'd do well to split the view into two parts: frontend source code and server-side source code.