Unfinished. All the points you raise are invalid. Tom and Yehuda are working very hard on ember itself. A RC is finally around the corner. Ember data will get the same treatment. It will take time. Ember data is more ambitious and complicated then ember.
I'm a platform engineer. I make API's that power web, mobile, and tablet applications. I also make the clients that consume then. You should hire me for any of these reasons:
* You need an API built
* You want to use Ember
* You want to use Rails
I prefer to work with tech companies. I'm available for remote work or possible onsite commitments in Europe (depending on location). I prefer short term contracts so I can deliver you something quickly.
Hey Patrick. Loved this post. Do you have any blog posts (or perhaps could write one) on handling consulting in remote locations? I know you're out in the middle of nowhere Japan. I'd love to hear your thoughts. Also what happened to the podcast? Seems to have got into hibernation.
> Great article but it fails to mention something important. A lot of 3rd party scripts use document.write. What this means is that even if you try to load them up asynchronously you will fail because the browser will wipe out the DOM when it gets to those calls.
The author is saying since Node is async by default and rails is not that, that node is better? For one, Rails neither async or sync. The programmer decides what to do. Two, Rails is a Framework, Node is a quasi language/framework. Want to do something completely async in Ruby use EventMachine. Zomg you're now async.
And really, MVC is no longer a good pattern for backends? That makes perfect nonsense. V = JSON, C = Things Interacting with HTTP, M = Domain Objects.
Out of curiosity, are they are any mature ORM's for Node? ActiveRecord has been around for quite a long time. You don't simply clone 8 years worth of development time.
World class backend Rails developer. 5+ years rails experience. Can build complete applications from the ground up or build API's to complement existing platforms. Experience with the full web stack. Active open source contributor. I know my stuff.