31–36 of 36 posts
At the end of the day, I want to write the least amount of code, have the best performance, and be able to have an easy way to test my code and all I had to do was get over putting extra code in my DOM and structuring my javascript in a way I wasn't familiar with. Browse the AngularJS source code and you'll see it littered with jsperf, they care about performance and you'll learn a lot about javascript performance. Y…
I really wanted to like Ember.js, but I had difficulties writing tests for my app and there isn't substantial documentation for it, which was a deal breaker for me.
We're using emberjs right now as well. But the lack of test integration is a huge problem for us. We right some tests with busterjs currently, but none of these tests are unit tests and tell us what exactly went wrong — somewhere.
So not to mis-read my comment: our application works and we deployed to production, and it's being used by customers, etc.. But whenver we need to dive into an emberjs-specific issue (e.g. we had a few regressions to fix which were introduced with the RCs) it gets messy.
If anything, the lack of testing (and currently lack of ideas how to integrate any) is the number one reason why I don't want to use emberjs again any time soon.
ember-data seems fine for us. Lots of conventions to adhere to (otherwise it's no fun at all). Once you figure out the side-loading, you're fine. We had to write a custom adapter so we don't have to repeat the things they call REST on the server.
But that part is solid and seems to work. :)
I really wanted to like Ember.js, but I had difficulties writing tests for my app and there isn't substantial documentation for it, which was a deal breaker for me.
This. We're using emberjs right now as well. But the lack of test integration is a huge problem for us. We right some tests with busterjs currently, but none of these tests are unit tests and tell us what exactly went wrong — somewhere. So not to mis-read my comment: our application works and we deployed to production, and it's being used by customers, etc.. But whenver we need to dive into an emberjs-specific issue…
For those of us not using Rails, here's a jsFiddle that shows how to test an Ember.js application: http://jsfiddle.net/ekidd/hCsws/
This includes both unit tests (for models, views and controllers) and full integration tests (using jQuery and chai-jquery to drive the GUI). There are one or two rough edges, which are documented, and which I plan to submit bugs about soon.
Earlier quoted context omitted.
I'm glad that, unlike the previous comment thread, you decided not to refer to Ember as "the North Korea of the JavaScript world." However, what you're doing here might best be described as presenting a series of "loaded questions." You can find out more about this logical fallacy here: https://yourlogicalfallacyis.com/loaded-question I'm sorry that you feel the need to attack Ember. If you have any specific complain…
He does have a point though (the NK reference is hilarious because it's actually not completely off-base, albeit a little over the top). I looked at Ember again the other day after a long abstinence and to me it has become frighteningly opaque. Even with my prior Ember-knowledge (before Router and {{outlet}} existed in their current form) I completely failed to make sense of a recent tutorial[1]. I wanted to wire the…
+1 on trying to track down errors. They never point to a line of user code! It's extremely frustrating when something breaks and you have no idea why.
Earlier quoted context omitted.
I also plan on doing some work to make sure that ActiveModel::Serializers will always work with the latest version of Ember Data. I've been spending much of my OSS time on Resque lately, but this is in my pipeline.
ActiveModel::Serializers is awesome! The convenience of having a 1:1 companion OSS package on the server-side to hook up with an ember-app is great.
Earlier quoted context omitted.
He does have a point though (the NK reference is hilarious because it's actually not completely off-base, albeit a little over the top). I looked at Ember again the other day after a long abstinence and to me it has become frighteningly opaque. Even with my prior Ember-knowledge (before Router and {{outlet}} existed in their current form) I completely failed to make sense of a recent tutorial[1]. I wanted to wire the…
I had almost the exact same experience. I originally used Ember 0.9.5 for an app and it worked very well. When I moved to 1.0.0-pre I felt that I had to completely relearn everything. +1 on trying to track down errors. They never point to a line of user code! It's extremely frustrating when something breaks and you have no idea why.