21–30 of 104 posts
So, isn't it time we had another Angular vs Ember discussion? I tried Ember some time ago and it just didn't click for me. It's hard to explain exactly why, but I found myself switching between too many files to get simple things done. I've done some simple Angular work recently, and found it a relatively simple system. In defence of Ember everything about the project -- docs, community -- seems to be better organise…
So, isn't it time we had another Angular vs Ember discussion? I tried Ember some time ago and it just didn't click for me. It's hard to explain exactly why, but I found myself switching between too many files to get simple things done. I've done some simple Angular work recently, and found it a relatively simple system. In defence of Ember everything about the project -- docs, community -- seems to be better organise…
How about we all try them first?
I said this already on Twitter, but: It’s been 2½ years since I started working on Ember.js. While I’m proud of the code we wrote, I’m even more proud of the community we built. We have been lucky enough to attract the companies and individuals that are tackling the hardest problems in developing 100% JavaScript web applications; people for whom the only acceptable answer is solid engineering, not piles of hacks. As…
Let's not use this opportunity to start another Ember vs Angular argument. Can we instead take a moment to celebrate the fact that we now have two major, stable, fast, capable, testable, tested, supported, documented, git-hubbed single-app javascript frameworks with large, passionate communities. Let's also recognise and celebrate the hard work put into these projects by the Ember & Angular teams. Ember and Angular a…
Does Angular really qualify here? Technically it's documented, but they're terrible.
Awesome, have been meaning to try ember. Just finished with a 6 month meteor.js binge. Which leads me to the question: what is a good real time push solution for ember? Does it have anything for that, or is that something I'd have to build in separately with socket.io or sock.js or something?
There is nothing built-in but it would be straightforward to update your model data over web sockets. The magic of Ember bindings and observers will take care of the rest.
While, true, Ember will happily update any model pushed to it the difficult bit i.e. pushing the right data to the right model (on the right client) and only the right model to only the right client is an exercise left to the reader.
The cleverness of Meteor is not in the push, it's in the logic just before the push.
I truly love this outstanding project and I'd like more people to join the ember.js community.
So, isn't it time we had another Angular vs Ember discussion? I tried Ember some time ago and it just didn't click for me. It's hard to explain exactly why, but I found myself switching between too many files to get simple things done. I've done some simple Angular work recently, and found it a relatively simple system. In defence of Ember everything about the project -- docs, community -- seems to be better organise…
I know, it's a terrible, horrible practice, but hear me out.
Learning Ember, especially at the beginning, required me to sort of rewire my brain about what goes where. It's "MVC", but the M, V, and C mean totally different things than they mean in Rails. Really it's more like MVCRT (model view controller route template).
I found all the different files extremely confusing at first, especially since each tutorial told you to lay things out slightly differently.
If you put it all in one file though, you can really easily move stuff around. You'll find yourself frequently pulling stuff out of a controller and sticking it in a view, or a route. Having to constantly switch files, remember where things are, create new files, and remove stuff from version control really puts a damper on things.
My advice to anyone starting with Ember: download the starter kit from emberjs.com and try to stick inside that as long as you can. You can just drop it into your Rails /public folder and get up and running.
Once you have a solid understanding of the architecture, and your app is getting bigger, it's literally an hour's work to pull everything out into separate files and drop it into something like the Rails asset system.
Earlier quoted context omitted.
There is nothing built-in but it would be straightforward to update your model data over web sockets. The magic of Ember bindings and observers will take care of the rest.
Saying it would be straight-forward is a little bit of an exaggeration. While, true, Ember will happily update any model pushed to it the difficult bit i.e. pushing the right data to the right model (on the right client) and only the right model to only the right client is an exercise left to the reader. The cleverness of Meteor is not in the push, it's in the logic just before the push.