Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Users Search
Help Dashboard Sign In Sign Up
Q&A Papers Meta
Meta
Posts Tags Edits
Create Post

Post History

71%
+3 −0
Meta React feature guidelines?

Summary "Outdated" should be used for "this won't work anymore today", not "we would do this differently today". Detail "Outdated" should be reserved for when an answer is wrong or misleading be...

posted 3y ago by Olin Lathrop‭  ·  edited 3y ago by Olin Lathrop‭

Answer
#3: Post edited by user avatar Olin Lathrop‭ · 2021-10-28T17:03:30Z (about 3 years ago)
  • <h2>Summary</h2>
  • "Outdated" should be used for <i>"this won't work anymore today"</i>, not <i>"we would do this differently today"</i>.
  • <hr>
  • "Outdated" should be reserved for when an answer is wrong or misleading because something has changed since the answer was written, and it's not obvious that the answer applies to the older situation. Using this for editorial reasons, like marking anything with an 8 bit microcontroller as outdated would be an abuse and NOT appreciated.
  • An example might be if someone asked how to define a curved trace in CircuitBarf. An answer was given at the time for the current version 1.0. If the answer no longer works in version 3.5, then it should be marked as outdated if neither the question nor answer otherwise make it clear they only apply to version 1.0.
  • Note that we try to avoid questions in the first place that are likely to result in answers that are quickly outdated. This is the main reason that shopping questions are not allowed, or questions about what the "best" microcontroller is for a specific situation.
  • This site is new enough that any answer to a valid question shouldn't be outdated yet. If such an answer exists, then it most likely is to a question that should not have been allowed in the first place.
  • <h2>Summary</h2>
  • "Outdated" should be used for <i>"this won't work anymore today"</i>, not <i>"we would do this differently today"</i>.
  • <h2>Detail</h2>
  • "Outdated" should be reserved for when an answer is wrong or misleading because something has changed since the answer was written, and it's not obvious that the answer applies to the older situation. Using this for editorial reasons, like marking anything with an 8 bit microcontroller as outdated would be an abuse and NOT appreciated.
  • An example might be if someone asked how to define a curved trace in CircuitBarf. An answer was given at the time for the current version 1.0. If the answer no longer works in version 3.5, then it should be marked as outdated if neither the question nor answer otherwise make it clear they only apply to version 1.0.
  • Note that we try to avoid questions in the first place that are likely to result in answers that are quickly outdated. This is the main reason that shopping questions are not allowed, or questions about what the "best" microcontroller is for a specific situation.
  • This site is new enough that any answer to a valid question shouldn't be outdated yet. If such an answer exists, then it most likely is to a question that should not have been allowed in the first place.
#2: Post edited by user avatar Olin Lathrop‭ · 2021-10-28T17:02:55Z (about 3 years ago)
  • "Outdated" should be reserved for when an answer is wrong or misleading because something has changed since the answer was written, and it's not obvious that the answer applies to the older situation. Using this for editorial reasons, like marking anything with an 8 bit microcontroller as outdated would be an abuse and NOT appreciated.
  • An example might be if someone asked how to define a curved trace in CircuitBarf. An answer was given at the time for the current version 1.0. If the answer no longer works in version 3.5, then it should be marked as outdated if neither the question nor answer otherwise make it clear they only apply to version 1.0.
  • Note that we try to avoid questions in the first place that are likely to result in answers that are quickly outdated. This is the main reason that shopping questions are not allowed, or questions about what the "best" microcontroller is for a specific situation.
  • This site is new enough that any answer to a valid question shouldn't be outdated yet. If such an answer exists, then it most likely is to a question that should not have been allowed in the first place.
  • <h2>Summary</h2>
  • "Outdated" should be used for <i>"this won't work anymore today"</i>, not <i>"we would do this differently today"</i>.
  • <hr>
  • "Outdated" should be reserved for when an answer is wrong or misleading because something has changed since the answer was written, and it's not obvious that the answer applies to the older situation. Using this for editorial reasons, like marking anything with an 8 bit microcontroller as outdated would be an abuse and NOT appreciated.
  • An example might be if someone asked how to define a curved trace in CircuitBarf. An answer was given at the time for the current version 1.0. If the answer no longer works in version 3.5, then it should be marked as outdated if neither the question nor answer otherwise make it clear they only apply to version 1.0.
  • Note that we try to avoid questions in the first place that are likely to result in answers that are quickly outdated. This is the main reason that shopping questions are not allowed, or questions about what the "best" microcontroller is for a specific situation.
  • This site is new enough that any answer to a valid question shouldn't be outdated yet. If such an answer exists, then it most likely is to a question that should not have been allowed in the first place.
#1: Initial revision by user avatar Olin Lathrop‭ · 2021-10-08T15:20:53Z (about 3 years ago) 
"Outdated" should be reserved for when an answer is wrong or misleading because something has changed since the answer was written, and it's not obvious that the answer applies to the older situation.  Using this for editorial reasons, like marking anything with an 8 bit microcontroller as outdated would be an abuse and NOT appreciated.

An example might be if someone asked how to define a curved trace in CircuitBarf.  An answer was given at the time for the current version 1.0.  If the answer no longer works in version 3.5, then it should be marked as outdated if neither the question nor answer otherwise make it clear they only apply to version 1.0.

Note that we try to avoid questions in the first place that are likely to result in answers that are quickly outdated.  This is the main reason that shopping questions are not allowed, or questions about what the "best" microcontroller is for a specific situation.

This site is new enough that any answer to a valid question shouldn't be outdated yet.  If such an answer exists, then it most likely is to a question that should not have been allowed in the first place.