# What changes should we make to the showcase before and after unlocking and reopening it?

We've reached consensus!

We'll make an exception and unlock and reopen the Showcase of Languages thread. In this (hopefully final) meta posts, we have to decide what this exception will cover, i.e., what changes we should make to the question before unlocking it, and what changes the community should make to the answers after it has been unlocked.

Below, there are a few answers that represent the different parts of my own proposed changes, which became the highest voted answer to the previous discussion. Because the community members might have cast their votes (or refrained from casting them) because they agreed with certain proposed changes but not with others, here you have the chance to vote for them separately.

Once the scores have stabilized, a moderator will alter the question based on those scores and unlock and reopen the thread.

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

• This is me. Since voting for too many proposals of a single user will cause the votes to get reversed, I'm using my fuzzy foot warmer. – Dennis Nov 28 '16 at 20:02

## Make it a non-challenge question

We do allow these, and the showcase is by far more similar to questions than to our usual programming contests. This should encompass unaccepting the answer with the highest vote count, removing the tag, and adding a dedicated tag which makes clear that this will be the only question of its kind, at least without a preceding meta discussion.

## 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. This is a huge deal on small screens or limited data plans.

• Stack Snippets can be expanded to take up the entire screen, making long answers substantially easier to read.

• Stack Snippets can contain more than just Markdown. An animated GIF is no longer the only way to show an animation, snippets could be fiddled with inline, etc.

• This is me. Since voting for too many proposals of a single user will cause the votes to get reversed, I'm using my fuzzy foot warmer. – Dennis Nov 28 '16 at 20:01
• I think this is one of the most important ones. Right now there's no point to reading most of the showcase because there's just way too much information to digest/scroll by. – James Nov 28 '16 at 20:16
• Additionally, a Stack Snippet could decompress and display a compressed string, allowing the 30k character limit to be bypassed. – Mego Nov 29 '16 at 1:52
• @Mego That's an interesting idea. Even if we want to keep the answers self-contained, a golfed version of LZString's decompression is less than 500 bytes long. Since it is a 30,000 character limit, we could take advantage of a big range of Unicode characters. – Dennis Nov 29 '16 at 2:04
• What about leaving the most recent/interesting code snippet out of the stack snippet along with the factoid? That way, people would get some idea of what sort of stuff is contained within. – El'endia Starman Nov 29 '16 at 3:27
• I agree with Elendia. We should have answerers select their favorite code snippet to keep out of the stack snippet. We're doing this to make the post easier to browse and read, but if we don't leave interesting content on the page itself, then we've just made it harder to read and browse. – Nathan Merrill Nov 30 '16 at 15:18

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

Converting the entire thread to community wiki means that all answers will cease to be the "property" of a single member of the community; all users that cross the required threshold are free to add snippets of their own, or modify and/or remove low-quality contributions of other users.

In case you're worried, this will not affect the reputation you have already earned.

• My main misgiving with this is that it removes a reward for contributing to the Showcase (those shiny green points) and contributions aren't attributed as strongly. On the other hand, making it CW significantly shifts the emphasis and focus from individual contributions to communal collaboration. Ultimately, though I don't strongly prefer either option, I lean towards making the Showcase into something that is crowd-sourced. I think this will benefit the Showcase in the end, hence this proposal gets my upvote. – El'endia Starman Nov 29 '16 at 3:24

## Combine answers in the same language (whenever possible)

Ideally, we would have one page per language, but there's no way to make that happen using PPCG's Q&A format.

Consolidating multiple answers in a single language into a single post should be done whenever possible, both to make finding and reading about your language of interest easier and to avoid multiple near-duplicate snippets.

One issue with this idea is the 30,000 character limit imposed on answers. We could request the limit to be raised; this would also benefit answers in exceptionally verbose languages which tend to not fit into an answer even for the simplest challenges.

• What if two people do the same language? – Erik the Outgolfer Nov 28 '16 at 20:25
• The answers will be combined and one will be deleted. – Dennis Nov 28 '16 at 20:31
• Well, I don't generally agree with that idea. I believe that the person who creates the snippets should have the ownership of them. – Erik the Outgolfer Nov 28 '16 at 20:33
• How does this work with the votes = byte length rule (which I don't see a suggestion to change)? There would surely be conflicts, – Calvin's Hobbies Nov 28 '16 at 20:38
• @ErikGolfer I'm also proposing to make the question community wiki. There will be no owners, just contributors. – Dennis Nov 28 '16 at 21:00
• @Calvin'sHobbies I overlooked that proposal at first. Yes, this proposal would pretty much require the community wiki and one vote at a time proposals to function as intended. – Dennis Nov 28 '16 at 22:06
• @Dennis Then I'd suggest also including the CW and one-vote-at-a-time removal proposals in this answer too. As it is right now, it seems independent from the others. – Erik the Outgolfer Nov 29 '16 at 11:49
• @ErikGolfer They are independent. Most of the changes I've proposed will work better combined with others, and hopefully voters will take that into account. I can't/won't change an answer after 16 members of the community have voted on it. – Dennis Nov 29 '16 at 14:29
• I like the rest of the proposals, but I'm not a fan of this one, as it often misrepresents voting. We want interesting answers to naturally float to the top, but if we just edit in new content then that new content is given free votes, regardless of its interestingness. This is a showcase, not a catalog. – Nathan Merrill Nov 30 '16 at 15:35
• @NathanMerrill The current format has the same issue. Just because voters liked the first X snippets you posted than guarantee they'll like the next X snippets too. The only way to make votes really meaningful in this situation would be to limit posts to a single snippet (or a fixed amount of them), but that creates a whole ton of other issues. – Dennis Dec 1 '16 at 0:11
• True. I've actually mentioned this elsewhere: I'd prefer the showcase to be one question per language, and one answer per snippet, but that's an entirely different issue – Nathan Merrill Dec 1 '16 at 0:20

## 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 doesn't seem to consider it a sufficient replacement. But once we find one, we could still revisit locking the showcase.

Downvote this if you think the exception to keep the showcase on PPCG is optimal or at least good enough, upvote if you think we should try finding a better solution.

• This is me. Since voting for too many proposals of a single user will cause the votes to get reversed, I'm using my fuzzy foot warmer. – Dennis Nov 28 '16 at 20:07

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