Introducing FunKiller

Question

I've invented a new language called FunKiller, which is designed to make radiation-hardening challenges trivial and boring. This is the JavaScript interpreter:

function interpret(s) {
  var lines = s.split("\n");
  var max = 0;
  var longestLine = ""
  lines.forEach(function(l) {
    if (l.length > max) {
      max = l.length;
      longestLine = l;
    }
  });
  i = prompt();
  eval(longestLine);
  alert(o);
}

As you can tell, it just finds the longest line in the file and eval's it. This means that I can trivially make any JS program radiation-hardened in this language:

alert(prompt()*2)

Becomes:

o=i*2


o=i*2

I certainly don't want this language to be used. Is this language valid for future challenges?

Answer 1

Is this language valid for future challenges?

Yes, the language became eligible to moment you published an interpreter.

But that's not a problem. radiation-hardening challenges are fun, but we do not need a whole bunch of them. The best challenges of this kind are innovative; they introduce a new concept or use one that has been recently introduced. For example, we have more than enough "make a quine that does X" challenges. Some offer a challenge, others just require trivial modifications of your language's payload-capable quine.

What I'm getting at is that challenge writers should try to come up with a spin of radiation-hardening rather than plain radiation-hardening. A FunKillerKiller, if you will. The tiniest change would make FunKiller useless for the challenge, as detecting the longest line would not be enough anymore.