Personally (obviously), I'm not a fan. In my opinion it goes against the spirit of challenging yourself to get a lower byte count if the language you're using is an existing language with the keywords shortened. In my eyes the only difference between that and using a language specifically designed to solve the challenge in a single character (e.g. HQ9+ for "write a quine") is scale.
I wouldn't support a rule against these languages. My idea of what constitutes a "good answer" isn't universal. If I downvote an answer because I don't like it but it gets a positive score overall, then it's a good answer. So sayeth the community, pretty much the only entity around here with an opinion that matters. I'm part of the community, so I throw my vote in, but your opinion of "this is 100% okay" is exactly as valid as mine.
The other(, less important,) reason is that it would be really, really difficult to make a fair rule. I don' think it's a good idea anyway, but even if I did: Where do you draw the line? Informally, in my head, I think about it the way I mentioned in the comments on your answer: The commands map 1-to-1 with the commands of another language. But that doesn't really work if you try to formalize it.
As I understand it (it's possible that I'm very wrong) a significant number of J commands are taken directly from APL. Is J a valid language?
In PYG, R
literally means range
. They're the same thing. But P
doesn't meant print
. P
means "print every argument to this function", a construct that doesn't exist by default in python. You have to define it in python, but in PYG it's already there. How much of a language has to be taken from another before it becomes invalid?
I'm not convinced that these are answerable questions, objectively. I have ideas of what I like and don't like, but it wouldn't even be possible to make those ideas into fair rules.
So while I don't personally like languages like PYG, I don't think we {sh,c}
ould have rules against them. People will upvote what they like and downvote what they don't, and at least for now that seems to be working out (for this specific issue, at least).
On a more personal note, sorry for starting shit in the comments on your answer. Almost all of the time, I downvote for this kind of thing silently (I know that you're supposed to leave a comment explaining how the answer could be improved, but "use a different language" doesn't seem constructive), but I was truly conflicted by my inability to upvote your python answer and downvote your PYG one.