Post History
Somewhere Else, there was a long-standing rule that to answer a challenge, you couldn't use languages, language versions, or features that were created or introduced after the challenge was posted....
Question
discussion
#1: Initial revision
Answering challenges with languages newer than the challenge
Somewhere Else, there was a long-standing rule that to answer a challenge, you couldn't use languages, language versions, or features that were created or introduced after the challenge was posted. If you did, the answer would have to be flagged as "non-competing." After some time, [the rule was seemingly removed by consensus](https://codegolf.meta.stackexchange.com/questions/12877/lets-allow-newer-languages-versions-for-older-challenges). The only real fear was that new languages would have some kind of advantage, but attitudes on the competitive aspect seemed to change over time (especially with golfing languages being created more frequently.) I haven't seen any discussion in this community (or a written rule) so I wondered what the public opinion is. Stated reasons on the thread for allowing newer languages: - Answering really old challenges with newer languages features. Otherwise old challenges would have to be reposted to allow newer answers, creating a bunch of duplicate content. - Competition generally occurs within a language, not all languages or classes of languages competing. People understand that Jelly will always beat Java, but one Java answer could beat another, or maybe a C++ answer. - "Catalog questions" like Hello World. - Adding a built-in to your language really only causes you more effort, and might be downvoted anyway if it's obviously created to solve one problem. Coming up with unoriginal answers is only less fun for you. - Some users would be discouraged from using newer languages.