Return to Question

So last time, I was hanging on codegolf, and came across the question Print the digital root, where one guy replied here with a one-byte code.

Of course, it takes advantages of the built-in and standard functions of the language, so it seems okay to end up with very short codes, in Jelly, Pyth, or such golfing languages.

But where is this gonna end?!

I'm actually pretty enthusiast with esoteric languages and such stuff, but if golfing's purpose is to find the shortest code possible, why couldn't I develop my own language, with my own compiler, where I would add one-byte functions every time a new golfing question is asked?

For instance, since s in Pyke means "Print the digital root of the input", what prevents me from creating a built-in function called そ that means "Spell out the input numbers in German" (although it might sound a bit Intercal-ish)?

Besides, I was scrolling the loopholes page when I came upon the Using a made-up language specifically designed for the challenge rule (whose title must be explicit enough). But if we do accept golfing languages, that are actually designed for golfing, this rule becomes null and void, doesn't it?

I am looking for something like a rule that says (though I doubt it can be clearly defined) where golfing begins and where it stops. Any thoughts?

So last time, I was hanging on codegolf, and came across the question Print the digital root, where one guy replied here with a one-byte code.

Of course, it takes advantages of the built-in and standard functions of the language, so it seems okay to end up with very short codes, in Jelly, Pyth, or such golfing languages.

But where is this gonna end?!

I'm actually pretty enthusiast with esoteric languages and such stuff, but if golfing's purpose is to find the shortest code possible, why couldn't I develop my own language, with my own compiler, where I would add one-byte functions every time a new golfing question is asked?

For instance, since s in Pyke means "Print the digital root of the input", what prevents me from creating a built-in function called そ that means "Spell out the input numbers in German" (although it might sound a bit Intercal-ish)?

Besides, I was scrolling the loopholes page when I came upon the Using a made-up language specifically designed for the challenge rule (whose title must be explicit enough). But if we do accept golfing languages, that are actually designed for golfing, this rule becomes null and void, doesn't it?

I am looking for something like a rule that says (though I doubt it can be clearly defined) where golfing begins and where it stops. Any thoughts?