38

It depends I think there are (at least) two very different cases, and the question as posed doesn't distinguish them. Case 1: banning languages the OP doesn't like Penalties for using "golfing languages" have a number of problems. For one, the question "Is XYZ a golfing language?" is subjective. For another, borrowing from a phrase about bringing a knife ...


35

Problems I see with locking the Showcase We have practically nowhere else to post what we can post on the showcase. You can always put them in the language's readme on GitHub, but I prefer the showcase because it's a ubiquitous place to post interesting snippets and tutorials. You can find a snippet about pretty much every language there, rather than having ...


22

The showcase is part of a unique category of pop-cons that should be on topic. Before I explain this, consider for a second why we banished code-trolling, underhanded and now are considering eliminating popularity-contest: site quality. During the great code trolling apocalypse, Doorknob and Martin made excellent arguments against it that more or less ...


17

Alternative phrasing for "Unclear": Please clarify the specification or add additional details to highlight exactly what is required. As currently written, it's hard to tell exactly what qualifies as a valid answer. It's especially important to be clear on I/O formats, guarantees about input values, and edge case behaviour. You may want to post your ...


16

I don't think the intention of the "answers must be competitive" rule ever was to close all questions which can't be improved on, nor does requiring closing follow from noticing a question which has an answer that can't be competed with. Should we also close a challenge with a 0-byte answer if it said "least amount of bytes wins, with tie breaker being post ...


15

No, it's too narrow We only get 5 custom close reasons. Let's save them for something better. The off-topic questions I remember that mention off-site programming challenges are just "help me with code" questions where the source of the question doesn't really matter. This is already handled by the custom close reason: This site is for programming ...


15

We should allow computational challenges of all sorts tl;dr: This site is about puzzles based on programming, not puzzles whose solutions are programs. This challenge qualifies. We currently accept a variety of challenges that are not based directly on code. For instance, we accept algorithm-only challenges. The accepted answer for why we should accept ...


15

Closing this challenge is pointless even if out-of-scope This challenge is still opened and… …it still receives interesting answers showcasing new languages. I still receive upvotes semi-often on that challenge suggesting that people are still interested in seeing languages snippets and explanations. What closing this challenge would do: Absolutely nothing ...


14

As someone who isn't a member of PPCG, but is a member of both Stack Overflow & Code Review (with relatively high reputation on both), I'd have to emphatically disagree with the wording of both options you presented. But ultimately, the biggest problem is that in your vote to close reason, you're recommending the user seek help at another Stack Exchange ...


14

Only for code golf I think disallowing non-observable requirements is good, but should be limited to pure code golf (without restricted-complexity for instance). As Nathan Merrill points out, many well-accepted challenge of other genres rely on unobservable requirements, and they shouldn't be accidental casualties of this rule. This leaves requiring "no ...


14

Replace "Primarily opinion based" with "Needs objective scoring criterion" We currently use a custom reason of "Off-topic" as "Needs objective scoring". That said, we receive many posts here that are attempting to be a challenge, but lack objective scoring. These challenges aren't "Off topic": they simply ...


14

Personally, I don't see any need to close old challenges that have ended, as people can still post (non-competitive) answers to them The "(non-competitive)" is a red herring. In a well presented KotH, anyone can (subject to being able to install all the necessary compilers/interpreters/runtimes) run the contest and reproduce the results. If this isn't the ...


13

That's a standard message Certain close messages are standard across all Stack Exchange sites and cannot be changed on a per-site basis. People who vote to close as unclear should specify in comments what exactly is unclear.


13

Having one of my questions being quickly close-voted for this reason, I think it shouldn't happen. Just because an answer is late to a challenge, I don't think it's bad or invalid. The late answers are often some of the best, since they aren't just quickly thrown together to try to win a challenge, but instead designed purely for the sake of deigning them. ...


11

I am divided on the "too trivial" issue, but would find it acceptable if it were worded in a way that is positively constructive to the user receiving it. Too Narrow There are either too few possible ways to answer, or answers would only differ in the language used. It tells users what went wrong. Some users will see this and explore their ...


11

No, don't close it, don't lock it If it ain't broke, don't fix it. Unless there are severe quality issues, don't let bureaucratic mumbo-jumbo get in the way of a challenge that many people are clearly entertained by on a site that (I believe) is, at-the-core, about entertainment — about enjoying programming.


10

Welcome to Programming Puzzles & Code Golf! I'm delighted that you've joined our community. Making a challenge is difficult and we have a lot of not-so-obvious guidelines about what makes them good and on-topic, but you've come to the right place for more detailed feedback! In this case there are three aspects of your challenge that generally aren't ...


10

As discussed on chat, when we started using custom "Off topic" reasons we lost the default one. But it would actually be useful. So I propose adding a custom off topic reason: This question is off topic for this site, as defined in the Help Center.


10

Unclear what you're asking means just that: it is unclear what you are asking for in your challenge spec. In almost all cases, further details should be left by the close voters as comments. While bonuses are discouraged, they don't make a challenge unclear, unless the specification of the bonus criteria itself is unclear. A do X without Y challenge doesn't ...


10

Close the robbers thread. If a challenge is closed, then no answers can be posted. cops-and-robbers challenges are made of two separate questions. Since we are closing challenges and not questions per se, we should close both threads, since otherwise robbing can continue even though the challenge is closed.


9

Too Broad There are either too many possible answers, or good answers would be too long for this format. Please add details to narrow the answer set or to isolate an issue that can be answered in a few paragraphs. I think this speaks most directly to the heart of the matter (emphasis mine). Without criteria to judge something valid or invalid, anything is ...


8

It is unclear I wasn't one of the voters, but given the current question state I would also vote to close as unclear. I've read the challenge description several times and I still don't know what it's asking for. Part of that is the challenge description, which consists only of the first paragraph, is all one run-on sentence. Breaking that out into bullet ...


8

Reopening takes time An unfortunate fact is that this site is not as active as it once was. That means accumulating the required reopen votes can take a while. What you can do The things I would recommend to do about this are Sandbox your challenge first. It is too late for this challenge but when a challenge is sandboxed issues can be addressed ...


8

The close reason is simple. You need details and clarity. There is no reason beyond that to close your question. Here's a few things you can improve, to be specific: You require a clear description of what an uncomputable number is, and maybe link to it. A single line description is not enough, and having more examples would help with understanding the ...


7

Rewording for "Duplicate" "This challenge has already been posted. It is either an exact duplicate, or the differences are superficial enough that an answer could be copied with minor modification from the existing challenge and be competitive here." Wording changes by @xnor


6

[R]ather than try to do some frankenscore of the program size and the compression size with some arcane mixing rule, a la the LZMA question, I just made the scoring all about the JPEG. Maybe if I phrased it "you need to generate the JPEG with code", it would be "about programming", but really, I don't care about saving bytes with esolang XYZ, and there are ...


6

First off, I'm sorry that your first contribution to our site was so poorly received. I hope this doesn't discourage from posting more challenges. Writing good challenges is really hard, especially for users who are unfamiliar with our rules and culture. But, they are extremely important for the health of this community, and something I personally enjoy ...


6

Rewording for "Unclear" "Please clarify the specifications of your challenge. As it's currently written, it's hard to tell exactly what a valid answer to your challenge would be. You may want to post your challenge to the Sandbox for feedback before submitting it on the main site."


Only top voted, non community-wiki answers of a minimum length are eligible