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 ...


31

Seriously though, historical locks are for questions that were on topic once, but became off topic due to a change in the site's scope. That's not the case here. Also, undeleting the question would send the message that this kind of prank is acceptable. That's also not the case; the user (sock) who posted that question was deleted for spamming the site. ...


27

Automate the catalog We should replace the manually curated answer list with a Stack Snippet. I hope nobody will actually object to this, but this should at the very least serve as a to-do list.


24

Let's make an exception This seems to be what the community as a whole wants. I don't think this is an optimal solution (and would personally to prefer to leave it as it is), but since the showcase is both too broad and dearly beloved by the community, it seems like a viable compromise. Below, I list some potential changes to the showcase that could both ...


23

Yes, Unlock and Reopen At least until we arrive at a more clear concensus on what to do with it, if anything.


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 ...


19

Make it a non-challenge question We do allow these, and the showcase is by far more similar to tips questions than to our usual programming contests. This should encompass unaccepting the answer with the highest vote count, removing the popularity-contest tag, and adding a dedicated showcase tag which makes clear that this will be the only question of its ...


19

Add a disclaimer: Note: New straightforward "Do X without Y" questions are not considered novel anymore and may be closed as duplicates of this question. But I think it should be worded better. Or as DJMcMayhem suggested: This question was well-received when it was posted, but challenges like this, asking answerers to Do X without using Y are likely ...


16

TL;DR: They are duplicates. Close the old one. First, I'd like to clarify that I do think the questions are duplicates. I agree with Peter that a difference in the output format counts as a "minor modification" to existing answers, unless the output formatting is the core of the challenge (which arguably it isn't in this case). So the criterion you're ...


15

Nothing is wrong with your question. There are questions with a lot more upvotes which haven't received answers in months or years. Your challenge has only been up for a few days, and due to the requirement for optimality it's moderately difficult. Sometimes it can take a while for answers to come in, and sometimes you'll only get one or two. Just keep ...


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 ...


15

Use Stack Snippets to fold answers Everything except the language name and a factoid could be folding by wrapping it into a stack snippet. That would condense each page into 30 stubs, which can be expanded with just two clicks. This serves multiple purposes: You don't have to load images of answers you're not interested in reading or have already read. ...


14

I don't think either one should be closed. The other one includes a ton of bonuses. While I don't think they are a great idea, they significantly change the challenge. Also, without the bonuses, the other challenge is only about handling a single type of bracket. Your challenge adds priorities to the bracket types. It's not only about correct balancing but ...


14

In this case, I think we can simply edit out the reference. The challenge itself isn't offensive, and you could substitute any word for POTATO without changing the task. "General policy" would follow suit IMO. If a simple edit can remove whatever's causing the offense, then just do it. If there's really no way to remove it, deletion might be a good option, ...


14

No, we shouldn't, but... I agree with the idea that we should not change a challenge unless the original OP wants to, especially when changing these rules might make older answers non-competitive. However, I am fully in support of the idea of a "canonical" challenge. Here on CGSE many of us, myself included, have developed our own programming ...


12

The code-golf tag wiki excerpt says: Code-golf is a competition to solve a particular problem in the fewest bytes of source code. If you want to score by characters instead of bytes, state this explicitly in the challenge. If source code length is not the primary scoring criterion, consider using another tag instead. While byte count is a part of your ...


12

The first five close votes, resulting in a close as unclear, were cast when the title and body contradicted each other. The next five, resulting in a second close as unclear, were probably cast in order to get more clarification on You may not use a loop, or use a constructions that is similar to a loop. Example of loop like constructions are GOTO and ...


12

Make a new category If the site benefits from this challenge, it should benefit from others like it. What if someone posts another showcase challenge that would be just as popular and well received, but never gets a chance to gather a following because it gets closed immediately? We should think about what qualities make such challenges valuable and ...


11

It Can Do Anything! While this is a great sentiment, it does leave the question without a meaningful objective. Every post will be one of its own, and it leaves loopholes open such as empty programs, which will be in hundreds of languages. Also, all challenges on PPCG require meaningful, objective criteria. This, as it stands, has one rule - use multiple ...


11

I can't speak to why the other users voted to close your question, but I would have closed it myself and here's why: First of all, it's more of an art contest than a programming contest. Challenges like that aren't on topic here since the site is about programming. Popularity contests, i.e. challenges which are scored by the number of votes, are difficult ...


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.


11

Make it a community wiki This is a perfect fit. Questions should be manually converted to community wiki when they are marginal fits or 'list of X' questions that contain enough value to avoid deletion. The showcase should obviously not be deleted, but it is a 'list of X' question, and considered too broad or even off topic by some members of the ...


11

Keep searching for better alternatives As before, I still believe that the showcase deserves to be a proper wiki, quite possibly outside PPCG, free from restrictions on character count, size, Markdown, JavaScript, pagination, etc. While there are existing alternatives – e.g., Esolang could showcase the recreational programming languages – the community ...


11

Remove the one vote at a time rule Additional snippets could be added at will and would not be restricted to one snippet per character count. I don't think character count should be a limiting factor at all; it hinders showcasing intentionally verbose languages.


11

Err... no. You should work on improving your challenge first. Your question is quite unclear, and fairly poorly formatted. By marking it as "On Hold", we signify to future users that challenges which aren't clear will be put on hold, and to further encourage the use of the Sandbox. You were suggested to use the Sandbox six minutes after the challenge was ...


11

Yes, we should open it up to all languages. Limiting languages is generally discouraged, even for restricted-source, which is why we always have a few joke answers in Lenguage and similar. Not only that, but languages where numbers aren't present usually struggle with handling big numbers as well, Good luck printing anything higher than 256 in BF, and most ...


11

Yes, let's repost The restrictive I/O format has been pointed out in the comments and the OP has responded. That's a cumbersome I/O format that makes many languages unable to participate. – Mego♦ Apr 2 '16 at 5:26 @Mego thanks for the tip. but in fairness to the current submissions, let's not go changing preferential specs on a 4 year old question – ...


11

I'm repeating some things from my last comment, but leaving them here for completeness. I think that now the requirements are much better The requirements are much less clear with the added edge cases, so I have closed the challenge for now. I went through and tested every single answer that I could (all but 2 of them without TIO links). Not a single ...


11

Personally I think your challenge's idea is good, it has already caused a creative answer in Logo but lacks more specific details. I think this comment with 7 likes under your post should give a clue: recognisable is very subjective, I'd suggest giving a reference ASCII version that has to be matched. I would suggest to clarify details as much as ...


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