5 ms·
Sure! It's Node.js (pretty vanilla Express) on the backend, but most of the heavy lifting is in the browser. After trying Angular, Backbone and Ember, we settle
by callmevlad 14y ago
Sure! It's Node.js (pretty vanilla Express) on the backend, but most of the heavy lifting is in the browser. After trying Angular, Backbone and Ember, we settled on KnockoutJS for multiple reasons (that's a whole post in itself), the main one being performance (though some may find that statement shocking).
- stevensanderson 14y agoLooks awesome - nice work!
- bsaul 14y agoI'd be really curious to read that post if you ever write it. When i saw the binding betweeen editor widgets and code, i immediately thought of angularJS bindings between model and multiple views, but i don't know KnockoutJS very well, so i'm really curious.
- ktavera 14y agoGood choice with Knockout. I use it in many apps because of how lightweight and easy to implement it is. I've hit some performance problems when tracking large number of observables but overall it can handles 99% of situations nicely.
- callmevlad 14y agoYep, that's been our experience so far. Believe it or not, but there are north of 100,000 observables on the CSS Playground page alone, so we had to really optimize things. It's still sluggish in some areas, though.
- tharshan09 14y agoI would be very interested in hearing why you chose that framework. Look forward to the blog post.
- stackthatcode 14y agoAs a KnockoutJS fan, this is completely awesome to hear. It's nice to see my technology of choice pushed to the limit. You guys have really delivered some phenomenal work.