> if you're writing something for other people to extend then using a well known framework as a starting point is a very, very obvious choice. This is precisel

> if you're writing something for other people to extend then using a well known framework as a starting point is a very, very obvious choice. This is precisely why we chose to build on top of Backbone.js. It has huge market saturation and easily understandable principles, but could benefit a lot from some of the killer features of Angular and Ember. Rarely does a framework do everything you need. In the eventuality that you create another app you'll want a custom platform to build off of. It simply makes sense to base that custom platform on top of something stable and vetted by the community.