Thanks everyone for replying!
@Nathan: I looked at (mainly) Angular and Ember before, but was fascinated by the simplicity of Spine.
It allowed me - an absolute non-JS guy - to get a fairly impressing result with nearly no learning efforts..so I sticked with it for the current project.
I didn't have those early-successes with Angular/Ember, through much more tutorials exist for these (but I did not find a single one talking about "complex" multi-page apps, while Spine.Stack makes this easy).
I'll see...
@Aaron: I saw that...but open pull requests from 2013 just look so scary! and fundamental stuff like the promises are still not available through a lot of issues from 2013-2015 have comments about them ("soon to be released"...etc.). :)
It is however nice to know that there's still a company? actively using it.
As said, I am pretty happy with Spine for the project I am working on (through it has some limitations like the missing promises, some "design" problems (e.g. if Ajax destroy() fails the record is still removed), but it's fine.
I'd really like to contribute, but I'm a bit helpless when trying to extend/improve the existing code base (would love to get some quick intro!!!)
..only sufficent enough for some small changes:
http://pastebin.com/3vFqth7q - fixed some coffeelint errors
- support for plurals ending in y -> ies
- nested Spine.Stack support
(but everything a bit hacky).
Problems I was not able to solve yet:
- overriding the model's save() method and simply calling super always resets the model
- if destroy() fails, it is still removed
- some refresh/change problems where data doesn't get refreshed
- missing promises (worked around)
So Aaron - do you think you'd have some time somewhen for a quick IRC/Gitter/Skype chat? That'd be awesome!