[KurtMueller]

I've heard the sales pitch for ember and ember-cli and I've seriously begun developing with Ember for the past 2 weeks. So far, I really like the tooling around Ember but am not a huge fan of the actual framework itself.

I mean, you have routers, routes, controllers, views, templates, and components - how many concepts do you need to display a ui?

Maybe it's just that I can't see the forest through the trees. Perhaps you could help me gain this perspective?

[andreisoare]

You have just one router, and that's only a config file that maps URLs to routes.

They're dropping controllers and views in a month, with Ember 2.0. They're being replaced by components.

So really you will only work with routes and components - which should make things much easier to understand.

[KurtMueller]

I know that there are talking about "routable components" with one-way data flow (ala react/flux), which hopefully comes soon. Are templates still being kept?

It seems like Ember is going to become a bit more like React (which I'm very fine with).