The result is always very noisy code that is just harder to read.
I’ve rolled up my sleeves and started coding again.
My development team on Crisply really doesn’t like front-end work. We’re solving some very interesting problems on the back-end and those problems are truly the make or break for the product. This made it easy to ignore the UI or at least to spend as little time as possible.
The one framework that stood out was Angular.js. It reminds me a lot of the data binding features in IE that my friend Sam Bent worked on. After much experimentation I feel that my initial instincts were valid. Although Ember.js is almost certainly more mature than Angular, I think Angular is a better fit for me and my team. It allows all us to write code that all of us can extend and maintain.
I’ll be most posting more as I continue to learn and hopefully master Angular but the primary goal is of course a working UI for Crisply.