points by giancarlostoro 14 hours ago | 0 comments
Honestly, if the "duplicate" question is older than 5 or 10 years they should force the mod to prove its resolved the same way before marking it duplicate.
[–] zahlman 9 hours ago
[–] braiamp 13 hours ago
Printing a string in python changed exactly twice. This is a 17 years old question about printing.
The top answer is still up to date
[–] giancarlostoro 11 hours ago
Sure, but that's not the case for every question. I've found questions spanning various languages, .NET is more damning because the mod didn't apparently know that .NET Framework and .NET Core are distinctively different, so the problem might "look" related, but its not .NET Framework and .NET Core were NOT compatible at all. .NET 5+ became a .NET Core rebrand, and .NET Framework is basically abandonware. You cannot import .NET Framework libraries into .NET (Core / 5+) projects, but the confusion comes from libraries that migrated to Core and beyond, so a problem looks "familiar" but its completely different runtimes and in some cases underlying third-party code.
[–] braiamp 6 hours ago
Which mod? Show the question
Generally, the people doing this are familiar with the material. Fast closures are motivated by an unconscious "ugh, not THIS question again". And the kinds of things that get asked over and over usually don't change very much.
There's a particular type of question asker who likes to say "what's the way to do this in [current year]?" as if to imply that it should be something different from before. But it very often isn't. And indeed, developers complain when languages/libraries/ecosystems change too quickly, which makes language designers/library authors more conservative about those changes.