Here's why: SO points are not based on complexity or thoroughness, but based on value - value that is perceived by the community. A quick answer to an simple Javascript question may seem rudimentary to an experienced programmer, but if it has hundreds of points, the community has determined that the answer is helpful in a big way. Chances are there are many, many people that have experienced the same problem, which makes an answer to that problem - no matter how simple - incredibly valuable to the community as a whole.
Edit: This is probably obvious for SO users, but it's worth mentioning for anybody that is confused or wondering why the point system works the way it does.
As you say though, you really can help people who have difficult questions in the niche tags (I've been spending far too much time in 'iokit' and 'objective-c++'). One upvote plus your answer accepted (total +25) is all you can hope for, though.
There's a ten-month-old widely-supported proposal on meta meant to address this, but it hasn't received any comment from the Stack Exchange Inc. folks. http://meta.stackoverflow.com/q/90620/134300
- rewarding with rep could convert answerers to closers
* answering produces useful stuff, closing is (often) just clerical
- over aggressive closing drives new users away
* blatant laziness shouldn't be rewarded, but subtle variations on a problem shouldn't be punished either
- some level of duplication is a good thing
* http://blog.stackoverflow.com/2010/11/dr-strangedupe-or-how-...
* in a nutshell, people ask the same conceptual question in different ways, it's good to have all those ways around to help Googlers
We've also improved finding duplicates in the close dialog since that meta post (it's a hard problem, so it's not a perfect suggesting system), so it's hardly like we've done nothing.
Also, as written that feature request is unworkable. Incentivize closing over asking, madness. Even incentivizing over editing (+2 up to 1k rep) is harmful IMO. I suppose we could just decline that post, but what'll probably happen is it'll be status-completed when we've come up with a better solution (which will be documented in an answer).
http://data.stackexchange.com/stackoverflow/query/65516/clos...
^ Based on the most recent data dump, somewhere around a 15 - 20% of closed questions (which are about 3-4% of all new questions). That sounds about right, honestly. I'm sure some stuff is slipping through, and we could make it easier to maintain these rates; but it doesn't seem like a pandemic of duplicates.
Oops, forgot the disclaimer: Stack Exchange Inc. employee, etc. etc.
Answered questions appear in Unanswered only if no answer has been voted up. If you see a question with a good answer, just vote it up and clear the clutter for the next person looking at the Unanswered section.
Any forum that welcomes new users is going to have this problem. The same kind of thing happened on Forrst, which should probably have been a little more resistant.
This is a tough one. There already is a system for dealing with duplicates, which is to vote to close as a duplicate, but requires 5 people to so vote before it will actually be closed. You could reduce that number, but there would probably be concern about abuse and mistakes if you reduced that too far. The thing is, it's fairly labor intensive to actually find duplicate questions, and ensure that they really are duplicates. In many cases, it's just easier to answer the new question, than to dig out the duplicate, vote to close, and then, if you actually want to be helpful, explain in a comment why the question is a duplicate (since beginners might not understand how the other question answers theirs).
I find this very annoying, too. I can understand why it would happen from the point of view of the asker: he might have found the answer on some other website 5 minutes later, or he might have just decided to find a workaround. Still, I think SO should remind people to accept answers (penalize them for having low accept rates) or have the most upvoted answer selected automatically after a while. Nobody wants to write detailed answers for someone who isn't interested in the question anymore.
There should probably be some mechanism by which moderators or other trusted users can, after a time, accept an answer for such abandoned questions. Perhaps questions thus answered would be treated slightly differently (and identified differently in the UI); the original asker could always return and override the proxy acceptance.
It does. Your accept rate is displayed under your username when you ask a question. Let it drop to low and other users will start complaining in the comments under your question, telling you to start accepting if you expect answers.
Completely with you on the "thank yous" being the biggest motivating factor; I wouldn't care about the site if it weren't for those. That said, if you want to get your rep up without lowering your standards, one option for the high-traffic tags is to go for bounty questions. That way, if you give good answers, you get a reward which is commensurate with your time/expertise, and you know that the asker both appreciates the complexity of their question and is very keen to have an answer.
http://gamedev.stackexchange.com/questions/26491/matrix-rota...
I'm the top answer-er for the Canvas tag, having answered around ~10% of all questions ever asked about Canvas on StackOverflow.
I would say that reputation numbers don't necessarily measure engagement per se in S.O. very well.
I've found that if I answer a general JavaScript question, even if its an absurdly simple one, I garner more reputation in a few minutes than if I I give a detailed answer to 2-3 in depth canvas questions.
If I wanted to pad my reputation I could definitely answer more general JS questions that crop up, but I really enjoy helping people with their canvas projects, so I sorta stick to that domain and try to help with my slightly-more-unique knowledge.
Anyway, reputation numbers aren't that important to me. At the end of the day, this is the only encouragement I need:
http://i.imgur.com/POZmt.png