this post was submitted on 08 Jan 2025
210 points (98.6% liked)

Programming

17787 readers
172 users here now

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



founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] Kissaki@programming.dev 10 points 2 days ago* (last edited 2 days ago) (1 children)

I asked 1 high-quality question in 2024, and it was closed almost immediately, and I haven't engaged with the site since.

If someone with 20,000+ karma has their nicely-formatted questions closed so quickly, what must the newbies and rank-in-file encounter? This is probably a big reason why it's declining.

It's a high quality question, yes.

The close as already answered elsewhere is valid though. It's not saying that the question is wrong; at least a decade ago StackOverflow explicitly allowed and encouraged asking the same question in different ways so they and their answers can be found.

It's about operator precedence. And the referenced question asks the same thing, about ?? and a comparison operator.

The head note says:

This question already has an answer here:

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


The header also mentions [previously] opinion based, so I looked into the question edit history. It most certainly was not a "high quality" question at the beginning - at the very least to the degree it looks like now.

[–] magic_lobster_party@fedia.io 8 points 2 days ago (1 children)

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.

[–] Kissaki@programming.dev 0 points 2 days ago (1 children)

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.

[–] magic_lobster_party@fedia.io 2 points 2 days ago

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.