Friday, November 22, 2013

Farewell, Disqus

tl;dr: We are removing Disqus comments from the AngularJS docs.

Problems with Disqus
Besides making it difficult to moderate off-topic or inflammatory comments, many comments are specific to past versions of Angular. We think the documentation should be versioned alongside the code so there's never a question of whether information is out of date.

Disqus has been great for allowing us to get feedback and allow developers to share tips about AngularJS, but we think there are better ways to do this now. You'll always be able to see the Disqus comments in past versions of Angular (<=1.2.2), but going forward, here's where we think the things previously posted in comments should belong:

Questions
Post questions to StackOverflow or the mailing list. They tend to get answered more quickly and stay up-to-date because of the active community there.

Bug Reports (Issues)
Bug reports should go on Github. It's useful to be able to see everyone's issues, workarounds, and the progress towards fixing them all in the same place. See the relevant section of the contributing guide for more.

Improvements to the Documentation
We think the best way to improve the docs is by directly improving the text. You can do this via the "improve this doc" button at the top of each page.




108 comments:

  1. Disagree! The docs have been useful only because of the comments. I think it was a step forward and removing is a bad idea.

    ReplyDelete
    Replies
    1. Your comment is the perfect example of why they took the comments out...

      Delete
    2. I completely agree with you, the comments are what made the documentation usable.

      Delete
  2. I'm cool with tying comments to versions, but getting rid of them entirely? Some of the most useful stuff I've learned has been from the comment threads. And most of it was the kind of discourse that really wouldn't have been possible within the doc format otherwise.

    ReplyDelete
    Replies
    1. Agree not any more! Give my comments back !

      Delete
  3. I agree in that the comments have been really helpful. But I feel that was in part because the docs were incomplete.
    I believe that comments are the lazy way of improving the docs but I feel they do more good than harm. If a comment is old an the documentation is clear I would just ignore it.

    ReplyDelete
  4. As new user to Angular, it's true that I was always confused as to which version did the comment belong. First thing I looked was how old are the comment I was reading. Versioning comments would be ideal, but stackoverflow is still a good option.

    ReplyDelete
  5. I agree with this decision. Too many useless flame and outdated "sarcasm" in comments.

    ReplyDelete
  6. As one of semi-solutions could be adding links to SO and GH with prefilled tags

    ReplyDelete
  7. The idea of directing questions to the forum/mailing list is great. After all, that is what the Forum is dedicated to: shared questions and answers.

    I strongly disagree with the suggestions of using StackOverflow for questions or even code snippets. StackOverflow is archaic. Developers should use the Forum to search or post questions and solutions. The source solutions should be links to Gist, Plunkr, or jsFiddle for the source or samples. Pasting large code snippets in the Forum or comments is USELESS.

    Finally, if we are going to have a `Improve this document` button, then perhaps we should also provider two other buttons:

    Button 1: Improve this document
    Button 2: Report a Bug (which goes to GitHub Issues with topic prefilled)
    Button 3: Ask a Question (which could go the Forum)

    ReplyDelete
    Replies
    1. @Thomas Burleson, "StackOverflow is archaic", that must be the saddest thing I've heard all day.

      Delete
    2. I don't know about archaic, but I will admit that on SO it's a problem for certain questions and discussions that even when worded properly, they get closed as "not a good question format" or "not constructive" etc. This limitation of post types makes SO not a good substitute for documentation.

      Delete
    3. "The idea of directing questions to the forum/mailing list is great."
      "StackOverflow is archaic."

      Not just the latter is the saddest it's also (and more disturbing) the combined claims that are utterly ridiculous. While I agree that Discuss is not a way to go, but docs as they are, aren't really useful. Take for instance this page: Module#config(). Completely useless as it doesn't even document parameters supported by example usage so one could actually know how to use these things.

      Delete
  8. The comments are what saved me on multiple occasions.

    ReplyDelete
  9. Thomas Burleson: "StackOverflow is archaic."

    I can't imagine what you would think is archaic about Stack Overflow. Especially when compared to a forum or mailing list (at least for asking, answering, preserving and maintaining Q&A).

    ReplyDelete
  10. I can't count how many times the disqus comments helped me find the way to do something or workaround a bug. I can see comment date in there and judge how old the note is and often when things change, replies to old comments mention it. That's really going to be missed. Wish you could even have it read only or something.

    ReplyDelete
  11. I have to disagree, comments on docs helped me many times. They could be linked to the version if you really think they are getting outdated, but don't let them disappear...

    ReplyDelete
  12. Github is not ideal (euphemism) for updating documentation. Contributing users should be able to make a quick change, moderators should be able to accept a quick change, other users should be able to see these changes without having to wait for a new release.

    Currently, when you want to update the documentation, you have to write markdown inside a JavaScript comment, do a pull request, search for the link to the CLA because the link is dead, sign the CLA, adhere to the commit guidelines (wherever those are), and then your pull request just sits there together with 182 others. And if/when your pull request is accepted, you have to wait until the next version of AngularJS to make it become visible. This makes it really discouraging to help.

    And the documentation needs it! In complicated sections, the top comments are all about how unclear the documentation is, followed by a top comment explaining concepts better.

    ReplyDelete
  13. What not setup a new disqus account for every new version to fix the issue?

    ReplyDelete
  14. I thought the disqus comments were overly negative and sarcastic despite how helpful they were. I much rather prefer to see the answers on Stackoverflow and have those kinds of comments filtered out with high quality questions and answers.

    ReplyDelete
  15. Disagree - while some of the comments were negative and sarcastic, they helped me out on a number of occasions. Wayyyyyy too much burden/overhead for the casual user to add/edit examples/info on github. There's gotta be a better way.

    ReplyDelete
  16. Comments are now disabled on this blog.

    Questions should go to stack overflow. Bug Reports should go to github, and improvements to blog posts should be done by directly editing the text.

    ReplyDelete
  17. Disagree. I know that I will only repeat what others have already said but I have to: the comments proved to be very useful for me and for others. Why not to have separate Disqus for each version of angular?

    ReplyDelete
  18. The comments helped me a lot, the documentation took me into troubles.

    ReplyDelete
  19. What a shame! The comments were always here to complete the doc, now we have to stick to Stackoverflow posting questions that would have been posted thousand of times. Seriously, bad choice guys.

    ReplyDelete
  20. Lame.

    Can't believe *you* guys created Angular. It won't kill listening to what the community says.

    ReplyDelete
  21. There were two problems with the comments:
    1. Some were becoming outdated with the new release
    2. Flame at the bottom

    However, the value add was there:
    1. Comments rephrasing docs that made more sense
    2. More examples in JSFiddle
    3. Ability to ask question right on the same page
    4. Ability to find answer right on the same page

    Going to StackOverflow and searching for an answer is not an improvement. At the very least, you can provide a link in the docs to the StackOverflow with the pre-populated query to get relevant Q&A for the topic I'm currently browsing in the docs.

    But I would think, curated comment section at the bottom of the page, provided more value for readers than StackOverflow. Forum-like widget with ability to label Angular versions might even improve the experience(can't recommend any service to offer this functionality atm).

    ReplyDelete
    Replies
    1. Oh, I hope everybody realised that StackOverflow questions doesn't have Angular version label as well.

      Delete
    2. Disqus as configurations that allows to change the thread identifier, which would allow to create a forum for each version with little change to the implementation.

      I agree that comments were chaotic on some module, but that also reveals consern that angular developper can be aware of.

      Also the forum could be used like on php.net documentation. Don't allow question or bug fixes posts, but keep only the ones that explain the fonctionnality in other terms, or the ones that gives solutions to implementation issues

      Delete
  22. I agree with removing comments section. The one addition which might be helpful is sort of a ping-back list section. A list of resource relating to the doc page subject. Some sections might be auto-generated i.e. hitting the stackoverflow api twitter api... and others might be submitted by users as links to external resources like the yearmofmoo.com website which has saved my ass a few times already. By default the lists would show each sections with a count label. onClick the section would expand to show a list of links.

    ReplyDelete
  23. I think it would have been better to disable the ability to post new comments and still show the older comments. I learned some really usefull stuff from those and I am really disappointed they are complete gone, since the documentation still lacks some of the examples that were posted below.

    ReplyDelete
  24. outrage! all the docs should have been fixed before removing the comments. comments helped us overcome documentation deficiencies. dealing with version discrepancies in comments is better than dealing with insufficient documentation altogether.

    you're telling us to look four places for answers when all we need is one good set of docs.

    ReplyDelete
  25. The reason comments were so inflammataory is because of the lack of qualiity of the docs. Don't get me wrong, the live examples and attractive layout is nice, but it could have done better had it added more complex examples and more detail on quirks of the library. Angular is one of the coolest frameworks I've ever used, but I feel like the docs are still its achilles heel. It's too late now, but I would've kept Disqus as a quality-of-docs borometer (not to mention a place for work arounds and links to releveant info). After writing this, I hope it's taken as constructive criticism rather than scolding. That said, you guys have an awesome library, keep up the good work!!!

    ReplyDelete
  26. I strongly disagree with this move. Granted some comments could get out of date it was an amazing and contextual way to ask questions, leave thoughts and more importantly read other's questions and answers. I've had countless issues resolved for me just by reading other's comments.

    ReplyDelete
  27. this move just removed the most helpful part of the documentation.

    ReplyDelete
  28. At first, I was like, ok that's ok, lots of comments were things like "who wrote this doc? monkeys?" and that's not cool for anyone. But then when I looked at the 5 word description for isDefined, and had so many more questions about implementation options; I really missed not having at least something more there. Simple things are not on SO, and complex things have like 30 very specific implementation questions (also sometimes written by monkeys). The only thing left is the myriad of tutorials and blog posts for all this stuff.

    Maybe it was a bad move to have comments in the first place. Wikipedia has no comments, and users that have something constructive are compelled to improve the entry. Sounds like the interaction model that is wanted here but unfortunately we all got used to them, so having them taken away after proving so valuable will just cause people to come here and say "who took away our comments? monkeys?". Maybe having a comment section allowed us to become lazy and critical instead of proactive and helpful.

    At least having someone go though and update the doc for each entry before removing comments from that page would have been a good idea; as good an idea as AngularJS is.

    ReplyDelete
    Replies
    1. "Wikipedia has no comments, and users that have something constructive are compelled to improve the entry." Yes it does. On the top of an article, there are two tabs, "Article" and "Talk".

      Delete
  29. This comment has been removed by the author.

    ReplyDelete
  30. Brilliant. I like this idea. Most of the comments were distractions.

    ReplyDelete
  31. How about fetching relative items from Stackoverflow and showing beneath the article? Version differences will be the bottleneck again though.

    ReplyDelete
  32. This is terrible decision! Only way you can make up for this is by providing stellar docs ASAP.
    AngularJS's doc has been so painful to read.

    ReplyDelete
  33. This is a very-welcomed change. 7-9/10 the comments were either in relation to an older version, awfully written, erroneous, or less useful than a similar conversion on the mailing list.

    Several months ago I put together a link package for my team of angular resources that includes several very helpful mailing list threads, github issue threads, and stack overflow threads. There was exactly 0 links to documentation comments.

    ReplyDelete
    Replies
    1. Can you publish your link package on a blog or forum post and reply here with a link ... please?

      Delete
  34. I loved the comments. They were entertaining, useful, and made AngularJS seem approachable and popular. Now I feel lonely reading the docs.

    ReplyDelete
    Replies
    1. Could not have said it better myself. Say what you want about the spam in the comments, most of it was actually quite funny.

      Delete
  35. Bad idea, comment are so useful, the best choose will be have comment for version in any system (disqus or not)

    ReplyDelete
  36. Most of the probles I was able to solve, I learned from the comments section.
    tl;dr I do agree removing disqus but keep the comments section in general!

    ReplyDelete
  37. Problems *
    Sorry for the bad spelling, weekend over here

    ReplyDelete
  38. I definitely agree with this change - it is confusing seeing comments that often referred to previous docs/versions of Angular.

    I would like to suggest that some people check out #angularjs on Freenode in IRC - we are a very helpful bunch, and you often get people who has experience using and/or contributing to Angular assisting with problems.

    ReplyDelete
  39. Comments are sometimes useful and sometimes useless and make us waste time. Comments with moderator would be great.

    ReplyDelete
  40. The Discus comments should be tied to the major version releases. SO is supposed to be an improvement? Where in SO do the questions even show the version that is being discussed? I don't see it. I have to look at the date and guess which versions are being discussed and then continue searching thru more questions to find what relates to the correct version. SO is a great resource, but acting like it is better than comments that are in the doc comments is ridiculous. This is a disappointing decision.

    ReplyDelete
  41. The article mentions the Disqus comments are still active <=1.2.2 e.g. http://code.angularjs.org/1.2.2/docs/api

    ReplyDelete
  42. Nice.. Now when I need to understand AngularJS syntax, I will just go to the source code and spend hours each time I need to understand syntax for filters, directives, select options, or other under-documented areas

    ReplyDelete
  43. Well, that's a huge step backwards...

    ReplyDelete
  44. I agree with the fact that they were usually even more helpful than the docs itself. Maybe it feels nice and organised for the devs but it's a lot harder to find answers for the people who actually use the docs. I see no value gained from removing the comments.

    ReplyDelete
  45. Basically everyone here is proving the reason the comments should be closed IMO, and it's for the better (it's 95% complaints and 5% good ideas). A for ever tabbing forward list of comments is not a good solution. Having a single set of documentation for all versions, again not good but has been fixed.

    Stack Overflow is a good option. I agree with Brian B, that the lack of version "tags" or otherwise within SO is a deficiency of SO and should be improved. I generally just ask people to include version information in their question or else refuse to answer. If code is linked via JSFiddle or Plunkr great, but I also ask that users on SO include their source since many times it's easier to find the post that way and if jsfiddle or plunkr are down for whatever reason no problem with dead links.

    For those of you looking for people to chat with about problems in near real time come join the IRC channel #AngularJS

    Having comments based on versions from 1.0.x and on doesn't really seem helpful when those comments can be misguiding. Seeing 100 people complaining about some free code they aren't willing to understand isn't conducive to progress. 9 times out of 10 if I couldn't find the answer in the docs or by digging into the source a little, after a quick Google I found it on SO, not in the comments. I for one am glad to see them go and am fine with the existing means of discussing with the community. SO has a set of rules that avoids pure opinion based posts and helps people get at the root of their problem. Honestly in all seriousness if you really don't like the existing solutions build your own the tools are in your hands.

    ReplyDelete
  46. A good alternative, but would require reworking the comment backend, would be to up-vote comments like SO. That way the valid comments that everyone finds really useful would be immediately below the content and easily found. The useless troll comments would be pushed down or possibly hidden. Having comments from users that are implementing real solutions is HUGE for the helping the community and getting projects completed. Letting lame comments by kids be the reason for completely removing such an important resource is so discouraging and actually harms the progress of the framework. There has to be a better solution than "go to SO and figure it out from there".

    ReplyDelete
  47. What a loss! While I've found useful AngularJS Q&A in SO, the comments on the AngularJS docs save a huge amount of time for learning AngularJS compared to sifting SO for the right explanation. When the words are not clear an example is needed. The Discus comments directly provide links to useful examples and more detailed explanations. We will lose the context and navigation if the explanations are on SO. (Perhaps we could have SO questions starting with the doc page name, like "AngularJS:Bootstrap - What do they mean by ..." to help find what we are looking for. Its not exactly good advertising though.)

    What is needed is a more active transfer process from the comments to the documentation. The GitHub approach to documentation sounds painful compared to Wiki editing. Improving the docs is the heart of the problem. How about a doc link to a matching AngularJS Wiki instead? I'm sure that has drawbacks as well, but it could be a way to unburden the docs pages and provide an easier way to get doc improvements (in the form of documentation instead of comments).

    ReplyDelete
  48. This comment has been removed by the author.

    ReplyDelete
  49. This is horrible. The comments were the only thing that made the Angular docs useful 90% of the time. I already know how to use Stackoverflow and forums. This is very disappointing!

    ReplyDelete
  50. Disagree, because the comments help cover lacks of information in the docs

    ReplyDelete
  51. i understand that disqus is no good solution on the long term, but maybe linking to the old version that still has the disqus with some mention "warning, deprecated comments" with help the transition until you have a better solution running.

    ReplyDelete
  52. :( comments solved my problems many times... it was a natural way for people to share knowledge and vote on what helped

    ReplyDelete
  53. "Improve this doc" button is not functional now

    ReplyDelete
  54. Though this may be seen as a disappointing decision, it does one wonderful thing: It forces us as a community to improve the documentation not just create comments. Everybody here agrees that documentation is terrible and has been. This is a community driven, community developed, open-source project. It takes time to get things aligned and proper documentation is one of those things. The fact this framework uses version-controlled documentation is WELL above other open-source frameworks.

    This is a great step IMHO. That being said, the one's who are actively contributing to the project SHOULD NOT be committing code that is not properly documented. That includes exposed API, guides, and tutorials. We cannot be expected to learn adjustments and new features and create documentation just as the active contributors are pushing a new RC.

    REPO OWNERS:
    New RC or new feature? Require documentation updates before merging the pull requests and REVIEW them. I know there have often been issues opened for documentation. Maybe we can consider a managed side project to improve the API docs bottom up. I would help with what ever little time I have and I bet others that have ripped apart Angular to understand it would too. Twitter @stephen_jb and GitHub: @sjbarker

    ReplyDelete
  55. I will also chime in here and say the comments were often helpful in addition to the documentation. It enables crowd-sourced augmentation to the docs. Many times the documentation is sparse and a comment will contain the additional questions / answers about a topic.

    For example - can ngInclude utilize caching or preloading? No mention of either word appears the doc page - http://docs.angularjs.org/api/ng.directive:ngInclude - typically someone will ask the obvious in the comments and another person will answer it.

    If you can embed a Stack Overflow widget on every doc page, or tag comments with the current version when the comment was created, maybe that would be better, but nixing crowd-sourced doc improvements altogether is no good.

    ReplyDelete
  56. This comment has been removed by the author.

    ReplyDelete
  57. My personal opinion is that comments hurt more than they helped...want proof? Ask someone the difference between a Factory and a Service. I swear, if I see one more "expert" that says "Services are a singleton and Factories create a new instance every time..." I might explode. Services are factories!! The difference is that a service is instantiated then stored in the provider cache whereas the result of a factory is stored. All providers are singletons.

    ReplyDelete
  58. We want beer, girls & comments in documentation!
    (and remove this stupid small menu on the right side)

    ReplyDelete
  59. Guess time is ripe for some good old docware

    ReplyDelete
  60. Bad decision. Bring comments back.

    ReplyDelete
  61. that's definitely a bad idea. I understand that some comments are outdated, hence cleaning all comments when a new major version has been realised may make sense, but removing comments altogether make our developer life just harder: if docs have been improved recently, they are still far to answer all questions we may have. And having to check angular doc, stackoverflow, mailing list, twitter, google, ... for finding an answer makes us not more productive.

    ReplyDelete
  62. I agree that the commentary that was spread across the "documentation" was out-of-hand, but that php.net - style of additions to the angularjs documentation was the only thing making it usable in a lot of cases. What it needed was aggressive moderation, not deletion.

    The stackoverflow-documentation idea is the worst idea to come from angularjs team yet: Don't get me wrong -- I use stackoverflow every day. But using a "seeking-help" forum as documentation completely misses the mark of clear concise examples tied to specific framework functionality. You cannot learn angular by browsing stackoverflow. Worst of all: since it is moderated by reputation and not framework designers, bad practices can be demonstrated and promoted as easily as best practices. It is no substitute for the right thing.

    ReplyDelete
  63. The comments were the only way I was able to learn to use AngularJS in a reasonable amount of time. The documentation by itself sucks. We're losing a wealth of information if the comments are really removed.

    ReplyDelete
  64. Agreed, Comments were not really useful and painfully outdated.

    ReplyDelete
  65. So dumb, the comments were actually more useful than the documentation itself! BLEH

    ReplyDelete
  66. In the past, the comments were are bad as the documentation. Once in a while you would find the proper, up-to-date solution, but half the time it would be an old answer. As an Angular noob, I am glad they are gone and I'm looking forward to improved documentation.

    ReplyDelete
  67. Those goddamn docs contained EXAMPLES and extra EXPLANATIONS missing from docs. Now you have removed it and the content which SHOULD be in the docs is GONE.
    So big F... thanks!

    ReplyDelete
  68. On Disqus, admins create communities. When they do, they receive an ID. When integrating Disqus into a web app, the developer uses the ID assigned to the community.

    So...how is it not possible to associate a Disqus community ID with each release of Angular and actually provide unique communities for each version? Would that (somehow) not solve the problem of ensuring each round of Disqus as most relevant to each released version of Angular?

    ReplyDelete
  69. Totally agree with the decision. Documentation is improving fast to quite useful state and most comments were outdated in both content and context.

    Both Angular newbies and advanced programmers should rather learn directly from docs and search forums / StackOverflow which are all actively maintained.

    ReplyDelete
  70. Whata... -_- Ouh boy... Comments is best thing about documentation... PHP documentation is probably best I seen because of comments. Boy I was happy Angular.js has same level of "quality" to their documentation pages. No documentation written by developer will be ever full... It needs LOT of feedback from community and you guys removed it... What you guys did is ruined your documentation.

    I am checking $timeout docs now, where are examples? Where are known issues? Where are tips and tricks?
    As for alternatives...
    Mailing list? Ah did not participate in any since nineties -_-
    Stackoverflow? Sadly they are not attached to Angular.js features, its different format from documentation...

    ReplyDelete
  71. this is the dumbest thing ever...

    i'm pretty sure the community can moderate themselves, that's the whole point of disqus, to allow users to moderate among themselves with votes.

    as for out of date comments... ... really?! VERSION YOUR DOC URLS!!!! problem solved. disqus works on a per-page basis, and if you version your docs then each iteration of documentation will have it's own comments.

    talk about shooting yourself in the foot...

    this is probably the dumbest move you all could have made, ever.

    huge step backwards, as others have said.

    angular already has bad docs, but to remove the discourse where we are attempting to help eachother... even worse.

    epic fail.

    ReplyDelete
  72. why does routeprovider don't support option 'requirement' and 'defaults' like symphony. i think its can be very useful for contrainst on the path

    ReplyDelete
  73. This is a terrible move, the comments are the best thing about Angular's documentation!

    ReplyDelete
  74. Things like this can greatly hinder people accepting a library/framework/project. Purely constructive criticism here, but why not just do your best to improve the docs? It's great that you all update Angular so frequently, but I think it would be better to have a library that is updated less frequently, with better documentation. So that way, you could spend more time making sure your users understand your library perfectly. Then, add incremental changes. You can make an amazing tool, but if everyone is confused on how to use that tool, people will give up on it. Having better docs would then minimize the amount of backlash from commenters. If everyone is saying docs suck, then it's not some conspiracy theory. Just my opinion. Also, I've never once posted a negative comment. The comments section was a perfect supplement to the actual docs. Oh well lol

    ReplyDelete
  75. I can't believe the comments are still gone, WHAT ARE YOU THINKING ?!

    ReplyDelete
  76. How about allowing Disqus comments on the current X(.y.z) version? This would largely solve the versioning problem, the out-of-date tips problem and the endless flame problem (rendering them existent but scan-able). if it's on the current version, then it's a nice relevant small set of comments is all that remains.

    ReplyDelete
  77. how can you remove comments... Everything seemed to make sense because of those comments.
    developers are referred to the right place to search for solutions to problems.

    WHY DO YOU TORTURE US SO!!!!!

    ReplyDelete
  78. This act will surely make the baby Jesus cry...

    ReplyDelete
  79. That sucks. Comments were some of the most helpful information available in the docs. If the angular docs had a bit more TLC we wouldn't have to rely so heavily on user comments.

    ReplyDelete
  80. I run the Ottawa AngularJS group so I'm a BIG fan of AngularJS. I know what a pain it is to moderate comments, especially if you start getting trolls, but I really wish there was some kind of stack-overflow type discussion mechanism because the docs just don't cut it for most people who are just starting to use AngularJS.

    ReplyDelete
  81. I just looked for an answer in the docs THAT I KNEW WAS THERE to a problem I was having, and after being unable to find it, I realized what I had actually been looking for was a specific comment that had thrown light on a quirk of angular's (latest version).

    Now that disqus and the helpful comment are gone, I'll have to find a workaround myself, create a new stackoverflow post, or post/spam the google group. I'm not sure how this is better in any way, shape, or form than the previous process of quickly scanning the comments.

    Furthermore, if the angular team couldn't take the time to edit/feed the actually helpful comments into the documentation before ditching disqus, how can you all expect your supporters to do the same? while i think angular is a brilliant library in a lot of ways, part of open source is community management and inspiring people to keep the faith and make it better.

    i wanted to be convinced that getting rid of disqus was a good idea, so i've withheld judgment. but after some time, what was obvious then is even more obvious now.

    getting rid of disqus was and is a bad idea.

    you all should be welcoming the (overly) incendiary feedback, not burying it in the sand and pretending everything in the universe of angular is brilliant and sunny. removing them is the opposite of lean startup methodology and strikes me as over-indulgent engineering rather than the process of people trying to create something revolutionary. to quote john milton:

    “I cannot praise a fugitive and cloistered virtue, unexercised and unbreathed, that never sallies out and sees her adversary, but slinks out of the race where that immortal garland is to be run for, not without dust and heat.”

    bring the comments back.

    ReplyDelete
  82. Disagree!! Comments below the Documentation would have been great!

    ReplyDelete
  83. The comments have saved me so many times by pointing out mistakes or omissions in the documentation. Without them the documentation in several places just won't cut it.

    I realize that managing comments is not a desired thing, but not having them is not a good option either.

    ReplyDelete
  84. This comment has been removed by the author.

    ReplyDelete
  85. Oh no lots of comments are useful

    ReplyDelete
  86. +1 for all people for who it was a big help like me... Maybe the presentations was not good enough, but the content was essential

    ReplyDelete
  87. I can understand why this may make sense, but.... WHERE ARE THE DISQUS THREADS??? I SURE HOPE I CAN STILL ACESS THESE ARCHIVES!!! THERE ARE INADEQUATE 'USAGE' EXAMPLES ON angularjs.org, ESPECIALLY FOR $controller. I WROTE TONS OF ENTRIES IN THOSE THREADS THAT ARE VERY HELPFUL!...?

    ReplyDelete
  88. I have to disagree as well. It would be a really a bad idea to completely remove all these valuable advices, hints and solutions from the comments which are often more helpful than the content of a certain document. At least try to find some compromise in order to keep some comments, link them or include them in the content itself.

    ReplyDelete
  89. you have an amazing framework here, in an important way because of it's community, please don't be control freaks! let the community thrive!!

    ReplyDelete
  90. please get comments back. Moderators can decide to remove unhelpful comments, but removing all comments doesn't make sense. and please try to write decent reference docs - not tutorials! tutorials are always good but they belong in tutorial section.

    ReplyDelete
  91. Comments were often more helpful than the docs. This is a step backwards.

    ReplyDelete
  92. I implemented a Disqus clone in angularJs in two days (minus account management, my app already had that). I think any comments engine could be added and linked to versions with out too much fuss. Moderation is the key. I like the StackOverflow decision. The comments were helpful at times, but I did get frustrated with older threads that just added noise and confusion.

    ReplyDelete
  93. Please bring the comments back in a read only fashion at least. They were REALLY helpful. Or at least bring them back until the docs are good enough.

    ReplyDelete

Note: Only a member of this blog may post a comment.