|
|
|
|
|
by pookieinc
4232 days ago
|
|
Haven't used Ember.js myself (though have been wanting to for quite some time). This struck a cord with me though: > 8. JavaScript > Writing most of your app in JavaScript is simly[sic] not fun. JavaScript is known for being designed in 10 days. Ruby is known for being designed for developer happiness - which sounds better to you?
--------- I don't think it's fair to compare Ruby and JavaScript because they are fundamentally used for different problems. You can never write Ruby for client-side, so why is it being compared? You have to use JavaScript (or CoffeeScript, or what have you), therefore you use it to get the job done. In essence, complaining why use JavaScript is not a fair reason against Ember. It's more of a reason for: "Why go with a client-side JS framework in general", rather than specifically Ember. This was the only point I wanted to make regarding the article. Aside from that, I definitely appreciate the learning and will take these reasons into consideration if/when I decide to use Ember.js. Hopefully one of the core team members can explain more about the other reasons mentioned. |
|