You need to make three things:
- Statement of a task, T.
- Solution of the task in language not typically used for golfing, A.
- Solution of the task in language typically used for golfing, B. Don't try to just bloat up B to pump up the score, instead think as if B was written by your competitor.
Use common sense in defining typically used for golfing
, try to maximize fun for other users.
Other users may propose better B
s (maybe including in other "golfy" languages).
Scoring is (length_in_bytes(B)+5)/(length_in_bytes(A)+5)
, more is better. (Maybe the scoring formula should be changed?..)
The main idea is to invent a task where languages that typically perform well in codegolf meet a problem. It can be sudden strength of a usual language in the given task or sudden weakness of some golflang.
Avoid tasks that mention specific programming languages, like Input a string and execute it as a Scheme code
.