You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since there's little room for more information on the README table, I propose the list be migrated to its own webpage (at https://ethproductions.github.io/golfing-langs or similar). This would allow more info to be displayed for each language; there could even be a small page for each.
The info to include for each language:
Name (including past/aka names)
Source (link to GitHub repo or similar)
Creator (including past/aka names)
Type (stack-based, prefix, etc.)
Specialty (perhaps just use the language page to expand a bit on its purpose)
Inspiration/origin story? (this would definitely be only on the language page)
Esolangs.org link (if available)
Documentation
Quick reference/cheat-sheet (perhaps archive some of the older ones—CJam's cheat-sheet was taken down a while back)
Online interpreter (TIO if it has one, plus any other up-to-date online interpreters)
Codepage (default, at least; e.g. Jelly supports UTF-8, but has its own default 256-char codepage)
Usage/popularity statistics?
Status (indev/stable/abandoned/etc.; would probably have to be updated manually)
Additionally, we could have a page for each language creator. This could include:
Main username
Real name (if available)
Additional usernames (past and/or aka)
GitHub profile
PPCG profile
Esolangs.org profile
Other profiles?
Suggestions are welcome for anything...
The text was updated successfully, but these errors were encountered:
Since there's little room for more information on the README table, I propose the list be migrated to its own webpage (at https://ethproductions.github.io/golfing-langs or similar). This would allow more info to be displayed for each language; there could even be a small page for each.
The info to include for each language:
Additionally, we could have a page for each language creator. This could include:
Suggestions are welcome for anything...
The text was updated successfully, but these errors were encountered: