142

StackOverflow has lost 77% of new questions compared to 2022. Lowest # since May 2009.(gist.github.com)

posted
by
Avatar
mesamune@lemmy.world
in
Avatar
programming@programming.dev
48 comments
hidereport
Sort:
HotTopControversialNewOld
You are viewing a single thread.
View all comments View context
Avatar
magic_lobster_party@fedia.io
6 points

Notably, it refers to answers, not the invalidity or duplication of a question.

I think it’s too much to close a question just because a different question happen to have the same answer. There might be a future answer that might apply to one, but not the other.

permalink
report
parent
reply
Avatar
Kissaki@programming.dev
0 points

Do you think that applies to this question?

Null coalesce operator vs comparison operator precedence? Both questions are about that. I don’t see one having a different answer to the other. In that case, duplication would only lead to spread out partially outdated information, instead of one place being updated.

permalink
report
parent
reply
Avatar
magic_lobster_party@fedia.io
2 points

Then it should be closed for being a duplicate question. I don’t think it makes sense to close any question for having a duplicate answer.

permalink
report
parent
reply

Programming

!programming@programming.dev

Create post

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person’s post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you’re posting long videos try to add in some form of tldr for those who don’t want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

Community stats

  • 2.2K

    Monthly active users

  • 1.9K

    Posts

  • 30K

    Comments

Community moderators