We are dealing with a very interesting question.
I feel that there are 2 different topics, and because of that, the perception may be different.
Topic 1: James playfully announced a challenge, the goal of which is to create a game by adding as little code (or as few lines) as possible. He himself tried to make the sizes as small as possible. It prefers to use a SELECT CASE instruction instead of IF, because it is well known that we are forced to press ENERT after the end of the IF line. Perhaps he considered the aesthetics of compression important and wanted to suggest that the program consists of 5 lines. It's a challenge. If we accept his rules of the game and what he asked the community to do, then different meaningful works can be created. A playful and creative process begins.
(this is what happens instead
)
Topic 2: usefulness of coding compression
Do I need a ":" character? should we cram everything together, or should it be more transparent? I think that it partly depends on the individual (to whom what is more transparent), and on the other hand, the complexity of the task also determines what is more beneficial for us. In the case of James's program, if development and comprehensibility are the goal (rather than player challenge), then compression is unjustified. You are absolutely right! There is a limit to this. It is also important to consider how big the program will be. If I were to leave the code blank when writing a program, the pageup and pagedown buttons would quickly wear out. I'll try to compress it at the very beginning.
We agree that if the basic principle is that the programmer's code can be understood by himself and others, then it is appropriate to express the plot in the simplest possible way.
I think everyone who is here on the forum has enough experience to decide what is beneficial for themselves and what is beneficial in the event that we want to share a code with others.
I feel that there are 2 different topics, and because of that, the perception may be different.
Topic 1: James playfully announced a challenge, the goal of which is to create a game by adding as little code (or as few lines) as possible. He himself tried to make the sizes as small as possible. It prefers to use a SELECT CASE instruction instead of IF, because it is well known that we are forced to press ENERT after the end of the IF line. Perhaps he considered the aesthetics of compression important and wanted to suggest that the program consists of 5 lines. It's a challenge. If we accept his rules of the game and what he asked the community to do, then different meaningful works can be created. A playful and creative process begins.
(this is what happens instead
)Topic 2: usefulness of coding compression
Do I need a ":" character? should we cram everything together, or should it be more transparent? I think that it partly depends on the individual (to whom what is more transparent), and on the other hand, the complexity of the task also determines what is more beneficial for us. In the case of James's program, if development and comprehensibility are the goal (rather than player challenge), then compression is unjustified. You are absolutely right! There is a limit to this. It is also important to consider how big the program will be. If I were to leave the code blank when writing a program, the pageup and pagedown buttons would quickly wear out. I'll try to compress it at the very beginning.
We agree that if the basic principle is that the programmer's code can be understood by himself and others, then it is appropriate to express the plot in the simplest possible way.
I think everyone who is here on the forum has enough experience to decide what is beneficial for themselves and what is beneficial in the event that we want to share a code with others.