Right up front, you should really be introducing people to the idea of using get() and set() rather than accessing properties directly. From the video (and accompanying text) it's actually not clear why you did that and it's one of the most critical pieces of Ember's "magic sauce." Aside from the data binding itself, it also ties you into things like computed properties and every introduction I've seen simply glosses over these methods. To me, they warrant a reasonable explanation so they don't appear to a newcomer as needless indirection.
To clarify, I'm a complete newbie at Ember. But I have done quite a bit of web programming before. I'd agree with you if this video is directed to people who are _completely_ new at programming and don't understand how to read documentation and how to use it, but it doesn't seem like this video is targeted at that audience (since he assumes you know html/css/javascript)
When I watched the first video, I saw you set the App.name like a regular property and then later I saw you use App.get/set.
My immediate question was: So does that mean that setting App.name as a regular property won't have the same 'binding' effect?
When you introduce two notations, but one is inferior (without an explicit explanation), that is confusing.
:-)
The apis used in these videos are frozen for ember 1.x, fortunately.
(I know your a bit tongue-in-cheek, but I appreciate a project that will replace difficult apis with reckless abandon as the community uses them pre 1.0)
(Or at least a link to your YouTube channel.)
Here is what I see: http://imgur.com/BcyVjhg
I hope that screenshot was useful. I just wasn't sure if I was the only one who was having trouble navigating.
Here are the instructions for building Ember Data (from a random YouTube comment):
git clone git://github.com/emberjs/data.git
cd data
bundle install
rake
You need to have bundler installed for your version of ruby.
Then go to dist/ember-data.js and use that where it says "ember-data-master.js" in the video. Worked for me.
In this case, adding a very brief overview of what Ember.js provides, and links to more info would seem appropriate.
Not everybody landing on that page knows what Ember is or why they might want to learn it, after all.
He should have at least a link to the Ember project page and some intro as to what it is.
Maybe he should have a episode 0 video which explains why should someone use ember instead of just jQuery or Backbone?
Good job.
The official guides are focused on ember-data with little information on how to use an alternative approach until it's stable for production use. This was very confusing for me (I'm in the process of rewriting an application at work in ember).
Can you provide some good/recommended practices/conventions on large apps so we can organize the file structures on the first try?
Just curious, is it a different effort from the embercasts?
How often will you be posting new videos and how many are you thinking to make?
Averaging that, I guess I plan on two per month.
https://tutsplus.com/course/lets-learn-ember/
It has 14 videos including a section that walks you through the making of a bookmark manager from scratch.
