151–160 of 252 posts
People 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.
Had 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.
Earlier quoted context omitted.
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.
You can see a list of features on the development version of the site at: http://beta.plnkr.co/ These include:
* Real-time code collaboration
* Fully-featured, customizable syntax editor
* Live previewing of code changes
* As-you-type code linting
* Transparent translation of intermediate languages like Coffee-Script, Typescript, Sass, etc (with sourcemapping included where available). This means you create 'app.coffee' and ask for 'app.js' in your html and you are served the compiled version of 'app.coffee' as well as its sourcemap.
* Forking, commenting (not done yet) and sharing of Plunks
* Fully open-source on Github under the MIT license
Also, there is both a Google Group (http://plnkr.co/discuss) and github repo (https://github.com/filearts/plunker).
That being said, neither of these properly address your question. I will push out an about page as soon as I can.
Trek 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…
I have admitted that, publicly, very often, in other topics on discuss.emberjs.com, on websites, on twitter, on videos, and elsewhere. It's no secret I'd like to improve the documentation for Ember.js and I'm already well aware of the places that people are facing difficulty right now. There's work, if people spent a moment reading the top topics in the forum, on a getting started guide with a direct call for feedbac…
I wanted to post this to your original comment there, but couldn't be bothered to make an account: "Get over yourself".
The guy was just (quite rightfully) venting about his frustration trying to get Ember to work, and the venting itself was still relatively tame. Besides, it wasn't a personal attack against you.
Pretending you're somehow above the discussion because of "the tone" is just lame, especially when there was nothing wrong with it. So much discussion is suppressed all over the world because people insist on latching on to how something was said, instead of whether there was any merit to it.
Earlier 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'm on your side here but I still have to defend trek on this one. This sort of feedback is not all that uncommon and at this point the Ember team has to be deaf, dumb, and blind not to know about it. Trek even says he knows about this and that they're working on it. And he's right that HN can sometimes be a place where people come to talk down to other people and rant like entitled assholes about asinine topics and…
The kind of feedback that has a point?
Earlier 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'm on your side here but I still have to defend trek on this one. This sort of feedback is not all that uncommon and at this point the Ember team has to be deaf, dumb, and blind not to know about it. Trek even says he knows about this and that they're working on it. And he's right that HN can sometimes be a place where people come to talk down to other people and rant like entitled assholes about asinine topics and…
Trek 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…
I have admitted that, publicly, very often, in other topics on discuss.emberjs.com, on websites, on twitter, on videos, and elsewhere. It's no secret I'd like to improve the documentation for Ember.js and I'm already well aware of the places that people are facing difficulty right now. There's work, if people spent a moment reading the top topics in the forum, on a getting started guide with a direct call for feedbac…
In general, I agree with this sentiment. But this post, which appeared (to me, at least) to contain extremely mild, non-personal-attack sarcasm, used to highlight areas of particular frustration, seems to be a shining example of how being 95% civil can result in much more effective communication than 100% civility.
If I were moderating that forum and wanted it to be a happy friendly constructive place, I'd let his post slide as a one-off, but give you a warning for being a condescending dick, since I find that kind of attitude in a community far more off-putting >_>
Earlier quoted context omitted.
I have admitted that, publicly, very often, in other topics on discuss.emberjs.com, on websites, on twitter, on videos, and elsewhere. It's no secret I'd like to improve the documentation for Ember.js and I'm already well aware of the places that people are facing difficulty right now. There's work, if people spent a moment reading the top topics in the forum, on a getting started guide with a direct call for feedbac…
You got feedback from a frustrated user, and I'm sure you didn't just dismiss it internally, so why did you dismiss it externally? Listen, I'd love to be able to write what I want, teach what I want, and do what I want without getting sarcastic reviews. But unfortunately people get frustrated and that's how they respond. "Oh, a tmux book? Who needs that?" "You suck" is very, very different from "the thing you built s…
But Discourse's goal is to raise the bar. Significantly. They blog rather eloquently about it http://blog.discourse.org/2013/03/the-universal-rules-of-civ...
And new topic posters are asked to keep that high standard in mind when posting. I'm sure his sarcasm was meant lightly, but it still deviates from the high quality of discussion I'd like to have, and rather than simply ignore a discussion where I was specifically invited, I opted to publicly explain why I wouldn't be participating.
What I failed to do, and this shows my failing to keep that high bar, is explain what we could change to make the discussion civil.
Earlier quoted context omitted.
Why was the Getting Started Guide not at (or near) the top of your priority list for documentation?
It is. http://discuss.emberjs.com/t/todomvc-based-getting-started-g...
trek: "I definitely feel your frustration. 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." Wow, could that response be any more passive aggressive?