The only truth I've seen is on the first page of http://batmanjs.org
It is _THAT_ easy :)
"Getting started with Ember.Js is easy." - No it isn't
61–70 of 252 posts
Re: "Getting started with Ember.Js is easy." - No it isn't
#62Had a similar experience, then tried AngularJS. Couldn't be happier :) http://angularjs.org
Same here, but let's be honest and admit that angular docs suck even more. Thankfully, there's a number of other resources one can find plenty of help.
Re: "Getting started with Ember.Js is easy." - No it isn't
#63In my personal opinion, I'd like to present a fair comparison with another similar framework called KnockoutJS. I challenge anyone on Hackernews to show me better documentation than this one: http://learn.knockoutjs.com Notice how things are explained so well as if they were explained to a child, this is how you should document, IMO. Also, RP Neimeyer, the creator (EDIT: Committer) of this framework, has dedicated a…
RP Niemeyer did not create Knockout. That was Steve Sanderson. Niemeyer has make but 9 commits to the Knockout codebase¹.
Knockout's tutorials are great. However, the rest of the documentation takes the form of other, slightly less helpful tutorials. The only API documentation is reading the code.
¹ https://github.com/SteveSanderson/knockout/commits?author=rn...
Re: "Getting started with Ember.Js is easy." - No it isn't
#64People rave about node.js and kock ruby. People rave about ember and knock backbone. But when it comes to building apps, the tried and true approaches are the best I've found. There is plenty of documentation online and that really helps when you are starting out.
When I gave ember a whirl, the lack of documentation, forums, or just anyone using it -- outside a core group -- was very disturbing.
Re: "Getting started with Ember.Js is easy." - No it isn't
#65Trek is making a huge mistake IMHO. As a developer I can think of nothing more helpful than to get a "steam-of-consciousness" excerpt from our users. This is something no analytics package can tell you, if you want to make your "product" easy to use then this is the exact feedback you need. Delverworld was outlining the various pitfalls of getting started with ember.js and a core contributor shrugs it off because he…
As someone developing a Javascript library, this a thousand times.
At some point I thought my library was easy to use and reasonably well documented for a very early stage library. Then I sat down at a little hack day with people trying to use it answering question over question about all those details that I had just assumed people would magically know, at the same time I though about for each of those questions there could have been hundreds of those that tried to use the library without me sitting next to them and gave up.
If I could get this type of feedback from every use, it would be amazing.
Re: "Getting started with Ember.Js is easy." - No it isn't
#66> The tone of this topic is not in line with the civil level of discourse I'd like to maintain here, so I cannot respond. This sounds like the euphemistic version of "I don't like your attitude, so fuck off." Not exactly the answer I would want to get as a new user who is stumbling over terrible and inconsistent documentation and error messages.
I agree that Trek's response here is not very helpful. However he has spent countless hours working on Ember's documentation and the fact that it's where it is now is due to his dedication. There's clearly more work to be done and we're all very well aware of that. We've been working on a getting started tutorial but it's been slow going since all of us on the Core Team are very busy with our day jobs. We hope to get something out for everyone as soon as possible.
Re: "Getting started with Ember.Js is easy." - No it isn't
#67In my personal opinion, I'd like to present a fair comparison with another similar framework called KnockoutJS. I challenge anyone on Hackernews to show me better documentation than this one: http://learn.knockoutjs.com Notice how things are explained so well as if they were explained to a child, this is how you should document, IMO. Also, RP Neimeyer, the creator (EDIT: Committer) of this framework, has dedicated a…
RP Niemeyer did not create Knockout. That was Steve Sanderson. Niemeyer has make but 9 commits to the Knockout codebase¹. Knockout's tutorials are great. However, the rest of the documentation takes the form of other, slightly less helpful tutorials. The only API documentation is reading the code. ¹ https://github.com/SteveSanderson/knockout/commits?author=rn...
Oh sorry, I didn't know that! But I see only him answering SO questions and writing blog posts 99% of the time, hence the assumption..
Re: "Getting started with Ember.Js is easy." - No it isn't
#68I'm always put off by the "look what can be done in just several lines!" code examples on frameworks front pages, they don't represent anything about the framework and usually the simpler the example, the more complex the framework is because everything is "magic" - try to do something differently and you end up hacking the framework internals.
It's especially offending when, as in this case, the bragging code-snippet omits half of the code that is needed to actually run the demo.
Ember is far from the only project guilty of this.
If you want to brag to me then make sure I can copy/paste your example to a file and it will run. I'll take a honest 50-liner over a dysfunct 10-liner any day.
Re: "Getting started with Ember.Js is easy." - No it isn't
#69Trek is making a huge mistake IMHO. As a developer I can think of nothing more helpful than to get a "steam-of-consciousness" excerpt from our users. This is something no analytics package can tell you, if you want to make your "product" easy to use then this is the exact feedback you need. Delverworld was outlining the various pitfalls of getting started with ember.js and a core contributor shrugs it off because he…
It's not the first time. I've been in their IRC. They are friendly and helpful. Especially Yehuda, but there seems to be this idea that if you "don't" get it, you might just be stupid...
http://twitter.com/trek/status/302811479135092736
I got this tweet and I constantly look at it before deciding against giving Ember another try.
So far I'v done Backbone, Angular and Batman and I've had no problems with either of them!
I decided to go with Batman.js unless I need extreme performance, then I'd go with Angular.
Embers concept of iOS seems broken. I'm an iOS developer. They don't follow the same pattern. The best they could have done would be to use the same API structure. But no...
"@Seivanheidari @ahazem we'd love to know the root cause of your difficulty. Most people seem to be successful with guides + api docs now."
Re: "Getting started with Ember.Js is easy." - No it isn't
#70Trek is making a huge mistake IMHO. As a developer I can think of nothing more helpful than to get a "steam-of-consciousness" excerpt from our users. This is something no analytics package can tell you, if you want to make your "product" easy to use then this is the exact feedback you need. Delverworld was outlining the various pitfalls of getting started with ember.js and a core contributor shrugs it off because he…
As someone developing a Javascript library, this a thousand times. At some point I thought my library was easy to use and reasonably well documented for a very early stage library. Then I sat down at a little hack day with people trying to use it answering question over question about all those details that I had just assumed people would magically know, at the same time I though about for each of those questions the…
Writing this I remember at some point for an old startup I used http://feedbackarmy.com/ to have people run through the getting started tutorial for my app.
When I get to release and am happy with the state of the documentation I will likely try the same thing.