I used Rivets on a decent-sized SPA and I have to say, it worked out really well.<p>The rendering was a bit slow, and in more than a few places I had to force a refresh to get it to pick up data changes. Those are really my only complaints though: the templates were a breeze to write, and with the ability to write custom formatters, Rivets is pretty expressive and extensible. I wound up with a codebase that was quite straightforward and easy to reason about, with minimal cruft. Overall I'd say it was a win.<p>Nowadays I use React.js and am very happy with the switch, but I definitely recommend Rivets to anyone who just wants to add a smidgeon of data-binding without pulling in a heavy framework. If I were doing that medium-sized SPA project again though, I'd definitely use React.
I really wish projects like this wouldn't register their own domain names.<p>The likelihood that vanity domains for new JavaScript libraries will still be renewed in 10 years time is pretty low - if they used rivetsjs.github.io instead there would be a much higher chance of links continuing to work far into the future.