Picking on transclusion seems really unfair. It's a well known rough spot in the docs and has been addressed in a bunch of places outside the formal docs that

Picking on transclusion seems really unfair. It's a well known rough spot in the docs and has been addressed in a bunch of places outside the formal docs that aren't hard to find. Plus, you can do tons with the framework without touching on it at all. To quote it, as the article does, as if its typical of the framework is disingenous. IME, the angular docs are way easier to understand than the ember docs and they're more accurate too. I've tried twice with the ember docs, and yes recently, and both times I gave up in eye-rolling wtf frustration. I'd love to use the framework, but there's only so far I'm willing to travel barefoot. The thing that bothers me most about this whole ember vs angular thing is that there seems like a crypto-subtext here. I'm not sure what exactly is going on but there's definitely an "open source mafia" versus "big corporate google guys" thing happening. I think, maybe, the fear from the open source mafia end is that google is going to cram deep support for angular into chrome -- this is not insane and would prolly make sense technically if not for those pesky standards -- and that ultimately this is going to do other frameworks a disservice. Wild speculation alert, okay, but still some politicizing of the the debate is definitely flying around here. I'd be happier if it were out in the open.