The all caps headline is a little too much for my taste.
Thanks to whoever changed it
"Getting started with Ember.Js is easy." - No it isn't
131–140 of 252 posts
Re: "Getting started with Ember.Js is easy." - No it isn't
#132This is all spot on. And despite the somewhat humorous, but not at all rude tone, this guy did some real leg-work to type this up. Documenting something in that much detail takes a lot of time (he went so far as to find the missing dependencies, and copied in the error messages at each step). Duck-debugging often works because you have to get specific, and logging issues is the same. I've had this same experience wit…
>> this guy did some real leg-work to type this up
This is important to note. The guy obviously wants to use Ember. To me that's a signal that if you help the guy out or address his complaints, that he might actually become a huge cheerleader for Ember.
I am guessing that for every guy who takes the time to complain, there are probably ten more people who just visit some library's site, try the demo and cruise the docs, and if it doesn't work, say "this isn't worth more of my time, next."
That this guy stuck around and detailed what needed work really does say something.
Re: "Getting started with Ember.Js is easy." - No it isn't
#133Had a similar experience, then tried AngularJS. Couldn't be happier :) http://angularjs.org
Same here. Just now, working on a project based on angular. Great experience.
Re: "Getting started with Ember.Js is easy." - No it isn't
#134I totally agree that our getting started story could be much better. In fact, it's our primary focus as we move towards 1.0. Specifically: * We're actively working on a Getting Started Guide with live examples that walks the user through building a new application from scratch. * We're continuing to improve our guides to talk through areas that might be confusing for new developers, like the naming conventions[1] we…
One thing I'm a big fan of is when projects have an always updated always working "Hello World" sample included with their project. This is something I've found to be common with iOS libraries and I think it would be helpful for you guys.
It's nice to be able to take a look at something that works and is simple enough to read through in one glance and go "Ah hah!"
Re: "Getting started with Ember.Js is easy." - No it isn't
#135Isn't all of this just blown out of proportion? Why not focus on how to help improve ember.js than one person's response? Even if that person contributes to the documentation and to the project. Get over it already.
It's incredibly out of proportion - but people really want to use ember (because it promises all these great things!) and they're frustrated by the docs (because they're not really good for first time users) so this is kind of a flash point.
Re: "Getting started with Ember.Js is easy." - No it isn't
#136I totally agree that our getting started story could be much better. In fact, it's our primary focus as we move towards 1.0. Specifically: * We're actively working on a Getting Started Guide with live examples that walks the user through building a new application from scratch. * We're continuing to improve our guides to talk through areas that might be confusing for new developers, like the naming conventions[1] we…
I'm very excited to see this naming conventions guide come out. I think you've done a great job here of clearing up in one place a lot of the magic that Ember does for you. Understanding how Ember looks things up is critical to developing nontrivial applications, so thanks!
Re: "Getting started with Ember.Js is easy." - No it isn't
#137Regardless of the technical difference between Angular and Ember, I have to say that the Angular documentation is one of the best I have ever read for a software library.
I'm not just talking about how it's written (it's English, it's technical, the bar is pretty low) but how they structured it to address exactly what the OP is complaining about: each code listing is shown in a multi-tab pages showing 1) the .html files 2) the .js files and 3) the .css files.
The only thing that could make it even better would be a direct link to a jsfidle (externally or internally hosted) so I can try and tweak all these examples without having to write my own, but it's already excellent as it is.
I hope more libraries follow this documentation model.
Re: "Getting started with Ember.Js is easy." - No it isn't
#138I totally agree that our getting started story could be much better. In fact, it's our primary focus as we move towards 1.0. Specifically: * We're actively working on a Getting Started Guide with live examples that walks the user through building a new application from scratch. * We're continuing to improve our guides to talk through areas that might be confusing for new developers, like the naming conventions[1] we…
> getting started story
Try talking like a human or at least a developer and not a marketroid.
Re: "Getting started with Ember.Js is easy." - No it isn't
#139Earlier quoted context omitted.
Sorry, but that's just ridiculous. You get some very detailed actionable feedback and flat out refuse to engage with it because it contains some mild sarcasm? No, obviously you would not like to help unless it's 100% on your terms, and you're not even telling which terms they are. Which is not very helpful at all and, in fact, showing a considerable degree of dickitude.
I have been following the ember.js community for awhile and also trek. It's this attitude that makes me never want to use ember.js. If you check out his twitter account, you can see countless battles with new people just getting into ember. If you want someone to use your framework, it shouldn't be a verbal battle of passive aggressiveness and other childish antics. He is doing a disservice to the community and the f…
"It's this attitude that makes me never want to use ember.js." Agreed. In fact, I suspect I'll never end up using it, now.
Re: "Getting started with Ember.Js is easy." - No it isn't
#140I totally agree that our getting started story could be much better. In fact, it's our primary focus as we move towards 1.0. Specifically: * We're actively working on a Getting Started Guide with live examples that walks the user through building a new application from scratch. * We're continuing to improve our guides to talk through areas that might be confusing for new developers, like the naming conventions[1] we…
If you guys are interested in putting together some usable examples (in the spirit of docs.angularjs.org), I would love to help you integrate live examples with Plunker ( http://plnkr.co/edit/ ). Bootstrapping an editor session is as simple as POST'ing a simple form targeted at that url. I would really love to see the Ember.js community get some use out of Plunker. (@filearts on twitter if you'd like to chat).
Does Plunker have an about page? I've been looking for a description of what it does and what it's for but can't seem to find anything.