This is an old but epic post discussing the pros and cons of each of these frameworks. I’ve been using Backbone heavily over the past two years and this quote really rings true to my experience:

I think Backbone is not a framework, when using Backbone you have to build a framework from the primitives it provides. This can be powerful or a burden and it mostly comes down to how much control you care to have.

In the end Ghost decided to go with Ember and the comments in the GitHub issue makes strong arguments for all three.

Not only does Apple provide an API for interacting with the operating system and install apps, but they also provide an Objective-C bridge to work directly with native libraries such as Cocoa. This is HUGE.

That’s why the fact that Apple is now offering JavaScript for task automation is so compelling. It’s not that developers have been dying to write more task automations, it’s that we have all long been searching for a universal language for building applications. The fragmentation in mobile has agitated this to nearly a tipping point. Nobody wants to install different IDEs, learn different SDKs, and maintain separate code bases. It’s simply not sustainable. Cross-compilation is appealing for this reason, but results in enormously bloated apps and a level of complexity between the developer and the operating system that they cannot control. If there is one thing developers hate, it’s a black box.

I totally missed this announcement but indeed it’s very exciting and could be a huge step for bringing web developers into true app development. Hopefully, it gets integrated beyond just Automator.

This update cannot be installed because it requires at least 6.9 GB of storage. You can make more storage available by deleting items in Usage Settings.

— iOS 8

EVERY iOS UPGRADE, EVER!