Ember CLI does file generation and a whole lot more. I'm not saying it shouldn't -- but that shouldn't be the easiest most approachable way to start with Ember.
Why should someone have to learn all the following things:
- transpiling
- nodejs
- npm & packaging
- bower
- broccoli/task runners
- livereload
... just to START with a web framework?
Maybe don't market Ember to beginners? Again, I like Ember, I think it's the most viable large framework out there right now -- but this is certainly an issue
Angular doesn't recommend any tooling, pretty much (just include the framework code and you're off to the races, write some html write some js)...
You can very well use React/Angular(1, atleast)/etc. just by including a script file in your markup and continuing to write your application code. There was a tutorial series for React posted on HN sometime before that made you learn React just this way.
And to be fair, the same thing has been said about React, though both Ember and React allow you to use a CDN link like in the good old days.
I started a new job and went from 0 JS (other than some JQuery and knowing the syntax) to 100 with Ember. Ember is really really good for beginners, grandparent talks of having to know transpiling, broccoli/task runners and livereload but doesn't understand that you need to know none of that to get working with Ember.
Write your app by editing the files ember-cli produces. No transpiling, or add transpiling with a single 'ember install' command. Who cares about broccoli, I just edit my ember-cli-build.js file with some paths and it all works. Livereload is hardly difficult to understand, with Ember you just run "ember serve" and it also all just works.
Also react's documentation is terribad. I'm in the middle of teaching someone who is completely new to JS how to use React, and the documentation has been horrendous (for newbies), reasons:
- JSX is super hard to properly understand if you only know HTML and JS and don't know they normally don't mix, and aren't actually mixing
- Requiring precompilation (no more JSXTransformer, no more babel-browser)
- The entire concept of components-all-the-way-down
- Documentation (Reference) section that does not differentiate between code blocks you can use and function signatures
- Hints on how to deal with routing
- No explanation of where to store data/state
I, as an experienced developer, can very easily understand React (I've used it on 2 projects now I think, and I like it), but there is so much for beginners to stumble on.
