Re:What does Stack Overflow want to be when it grows up?
by Bartweiss on Monday October 22, 2018 @11:27AM
(#18275417)
Pretty much all database questions have a severe case of this.
Huge swathes of features appear at transition points like MySQL 5.5 -> 5.6, which means lots of answers are now viable but no longer the best option. And since they are still correct, it's hard to write up new questions which won't be closed: instead of saying "Answer X no longer works", users have to say "Is Answer X still the best approach?" and get closed for duplication or subjectivity.
Worse still, lots of databases still have multiple versions in active use, so "worked great for me! - posted yesterday" isn't even a helpful reference.
Huge swathes of features appear at transition points like MySQL 5.5 -> 5.6, which means lots of answers are now viable but no longer the best option. And since they are still correct, it's hard to write up new questions which won't be closed: instead of saying "Answer X no longer works", users have to say "Is Answer X still the best approach?" and get closed for duplication or subjectivity.
Worse still, lots of databases still have multiple versions in active use, so "worked great for me! - posted yesterday" isn't even a helpful reference.