For my final WDI project I made a cheat sheet editor, using Ember.js for the editor itself. The original intention was to use Ember across the entire site. I was using the Ember data DS.RESTAdapter to sync with my Rails app but ran into trouble trying to adjust the API endpoint for particular queries… cue the pain.
Reading through the RESTAdapter documentation was fruitless - it appears this use case isn’t covered yet (to be fair, the RESTAdapter is currently described as alpha-quality on GitHub). I was faced with writing a custom adapter, but felt too short on time to embark on a rewrite of the rest of the project.
Here lies my grumble with Ember. There’s too much magic and there are lot’s of features still under development. Behind the magic lies a world of pain as soon as you need to alter something - if you’re still learning the ropes of Ember.
trodden tutorial-ed path and become very lost.
I have learnt more about Ember during the project, but I want to investigate Backbone.js because it looks like you need to build more of your app from the ground up. The ground-up approach should make it less likely that you outcode your current understanding of the framework.
At least you get to build the forest that you end up getting lost in and might recognise a few trees.
On to Backbone.js…
I’m working through Addy Osmani’s book on Developing Backbone.js Applications (it’s free to read online) so I’m looking forward to understanding how the frameworks differ.