Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

See https://meta.stackexchange.com/a/164449/192171

If an answer is factually wrong (as opposed to just poorly formatted or missing a few details), generally its better to leave a comment rather than try to edit it.

I agree its not ideal, but suggested edits go into a site-wide review queue, so not everyone reviewing them will necessarily be familiar with C. This makes edit reviews a poor tool for evaluating factual correctness; the comments section and voting system on answers is a better tool for that job.



"We must fix grammatical errors and must not fix technical errors" agrees with my experience on stackoverflow perfectly.


Fixing technical errors is strongly encouraged, just not via the suggested edits feature. Like I said, a comment or an alternative answer would be more appropriate.


If the fix is buried in a comment or lower answer, far fewer people will see it, especially on the ossified, highly-voted answers where it's often needed. Difficulty moderating proposed edits is a process problem, and comments aren't a good workaround.


"You can comment" doesn't help when you need a certain rep threshold just to comment.


Don't you need more to propose an edit?




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

Search: