4 ms·
>And the obsolescence, things are moving so fast in JavaScript, Android, even in QT, Clojure etc, many answers including accepted ones are obsolete, and mislead
by pytester 7y ago
>And the obsolescence, things are moving so fast in JavaScript, Android, even in QT, Clojure etc, many answers including accepted ones are obsolete, and misleading.
This is the absolute worst aspect of the site to me. Some answers are version specific, some stop working overnight one day, some used to be good practice in 2011 and still work but really aren't any more and there is no sane mechanism for stack overflow to handle any of these things.
This is quite apart from the multitude of answers which are voted to the top which are wrong, only partially right or bad answers.
- mLuby 7y agoRunnable code snippets are helpful in this regard, but even better would be runnable test cases. Example: How to check for Invalid Date in JS? ```js function invalidDate (date){return isNaN(date.valueOf())} console.assert(invalidDate(new Date("foo")) === true) console.assert(invalidDate(new Date()) === false) ``` But I'd expect if someone noticed an out-of-date answer they'd just comment and it'd get fixed that way.