HN2new | past | comments | ask | show | jobs | submitlogin

A quick note for that first tutorial (which is quite good already):

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.



I'll be honest, I like it this way. Looking up documentation for get() and set() is easy. What's hard is understanding how to use it. Had the video gone over this, it would be an extra 1-2 min long, and would be less direct.

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)


Solid point I considered carefully. I decided to bet on people watching the second video and keeping the first as bare-bones simple as possible.


Great videos, but I agree with the OP.

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.


Ah, well done then if it's included in the second video! Being at work, I didn't really have time to get that far. :)


Good job. As make more videos, will you be using ember-data or pure ajax like discourse did.


I'll use both.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: