I am currently working on a golfing language. Do you have any suggestions for this language? What are some helpful features of a good golfing language? What features do you find useful? Do you suggest a language based on variables, stack(s), tapes, registers, etc?

As usual, please post separate tips in separate answers.


closed as too broad by Geobits, Martin Ender Apr 29 '17 at 17:15

Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

  • 3
    \$\begingroup\$ I think this is too broad. We used to have this question which was more specific and we decided that this kind of question is not a good fit for the SE platform. Specific questions about the design of golfing languages could potentially be on-topic and well scoped, but I don't think this is. \$\endgroup\$ – Martin Ender Apr 29 '17 at 17:15
  • 4
    \$\begingroup\$ @MartinEnder If tips for golfing in <all langauges> on-topic than why isn't this? \$\endgroup\$ – programmer5000 Apr 29 '17 at 17:24
  • 2
    \$\begingroup\$ @programmer5000 That's a narrower question, since the tips there should pertain to the majority of languages, specific to shortening them. This one is completely open-ended, and answers could encompass the entirety of language design. \$\endgroup\$ – Geobits Apr 29 '17 at 17:34
  • 1
    \$\begingroup\$ @tkellehe Posted \$\endgroup\$ – programmer5000 Apr 29 '17 at 17:40
  • 1
    \$\begingroup\$ This question is now a duplicate of this one. @programmer5000, why didn't you just edit this question instead of posting a new one? \$\endgroup\$ – mbomb007 May 2 '17 at 15:20