It's really based on your "coding style" on how to reduce or limit the coding variable language used, and for the sake of an "idea", we can insert the word "updated version". (Just a comply) Good luck

Lesson learned: vm.runInNewContext is slow in js. :) Wonder if it was the context switches.

Fixed

Might be worth updating the node version here or explicitly marking it in the task description. Node 0.10 is considered very out of date by now.

@macobo, no worries; there doesn't appear to be any controversy. Valid points were addressed, no objections were made, and the thread remained civil, so the outcome appears to be positive.

Thanks for re-enabling require and sorry this turned to be a source of controversy.

I think the question to ask when disabling things is if helps with what the Kata is trying to teach? Sometimes you do want to teach people how the tools they're using under the hood work and these make for great taske.

In this case however, the task is not made easier as there's no library for doing exhaustive search. Using libraries here however allows users to write cleaner code, better reflecting what they might write the real world.

Anyways, just my opinion. YMMV. Thanks again for working on this task! :)

@Voile, admittedly I was being a bit fatuous but I see your point.

Okay. Let me open that cage and release the beast ;-)

That's not called "easier", that's called "less annoying".

I'd have no problems banning require in a kata about big integers for obvious reasons, but not here.

@myjinxin2015, if you think require should be allowed, feel free to make the change.

@macobo's first bullet point points to the contrary.

Why? Leaving require there does not make the kata any easier.

@macobo I disabled require for this kata.

Happy coding ^_^

Thanks ;-)