Exactly the same here. I really wanted to like Ember, since I liked the documentation and read a bit about how the project started and how it works on a higher level. However, since I couldn't get through the Get Started tutorial, I gave up and went into angular instead, and I haven't looked back.
I'd like to give Ember a second chance, if only so I could be the only person on the internet that has tried both angular and Ember on a deeper level, but right now I'm not sure I'd do any better should I actually try again.
I reviewed both angular and ember for integration with a rails app for my job recently: https://github.com/et/ember_vs_angular
To my dismay, we went with angular. In retrospect, after playing with the framework, I'm fairly pleased with the choice.
Same here - well documented although a lot of technical stuff involved but the fact that they use git for tutorials is nice. Loved playing around and being able to revert my changes back to the original state.
Angular is really great, just used it on a project for work. Didn't take long to pick up at all and I had things humming along in a few ours. Their documentation is pretty nice and there are a ton of great tutorials.
Same for me as well, I had previously used Backbone heavily at work (which is still awesome), but wanted to try something new. Angular has good docs, tutorials, screencasts and a very active Google Group with pretty helpful people.
Same here, but let's be honest and admit that angular docs suck even more. Thankfully, there's a number of other resources one can find plenty of help.
I'm interested by this because there is a huge amount of documentation for Angular and it's pretty good, including examples and plunker/jsfiddles to demonstrate it and allow you to play with it. What did you find lacking?
My first and strongest point isn't really the text itself, it's the organization and more "down to earth" examples. Google and it's products have historically poor UX, and Angular is no exception.
When you get to the page, you have 'develop' and 'learn' buttons, which one should I choose, I'm developing and learning at the same time. Okay, being new, let's go with tutorial. It says I should install testacular without any explanation how to organize files and tests in order to be effective. Moving on, okay, the tutorial is pretty basic, but wait, we're building an "app" so there must be some kind of session system, where can I find it? No clue.
What I'm trying to say is that two important things are missing, first a more "global" overview, a story, a use case for the angular itself, not just a number of isolated examples. Second, a nicer design for the docs, look for example this: http://www.chartjs.org/docs/ - It's one dude and he can do better than Google with pretty much unlimited resources?
I know many people compare Ember.js and Angular and while I prefer Angular by a wide margin, Ember's landing page wins hands down - it has soul. Angular has Twitter bootstrap.
I'm getting the feeling that Angular has now become the Haskell of client-side frameworks.
i.e. the one you'll see shamelessly plugged under every single discussion about any other client-side framework as if it is some work of genius, even though lots of users tend to agree that it's just yet another take on the subject that some like better and some don't, with some very lacking and outdated documentation and a much stronger and opinionated take on things that is simply not everyone's cup of tea.
With all due respect to the fantastic project that is Angular, I just wish people would stop flashing it everywhere like it's going to solve world hunger and programmer distress or something...
I don't think the parent post was suggesting anything of the sort. Instead of claiming to solve world hunger, it looks like AngularJS makes it possible to actually get started if you're new to this kind of framework.
I haven't tried Ember nor Angular yet (Ember because of a lack of documentation and Angular because I basically didn't hear much about it till today) but at this point, I'd use Angular simply because their website actually looks like it has a quickstart/tutorial that works.
In part, it's relief. the Angular project has relatively minimal functionality and therefore does it quite well. The documentation is adequate (there are a few places where there are 'magic settings' which aren't immediately obvious, plus it pushes you to write tests.
