Enabled in this fork

this kata is more than 10 years old. Classes were introduced in ES2015. (by the way, classes are no longer merely syntactic sugar for prototypal objects; private class features for instance can hardly be emulated with pre-ES2015 JavaScript)

why not use a class? I get that a class is just syntactical sugar and it's doing this under the hood but why do it like this?

Loved this kata! Very good and interesting description, clear task and easy to understand solution. I wish there were more katas like this one ^^

Good one with the prototype. but if the object will be created with the class, the prototype is created automatically.

Thank you for having specific and clear description what this Kata asks for. In contrast, I often feel the descriptions of several Kata(s) especially those in OOP tag are often ambiguous, resulting in taking more time for me to figure out what Kata asks for than actually thnking abut the code.

I figured it out, but the long winded description sucked the energy out of me and it took me a rest to get up to speed with the slight mathematical thinking that this kata needs

C++ Translation

Cool kata! :)

This should really be 8 kyu

done, but the description's markdown code is starting to be really bloated...

duplicate issue

added to Python, Ruby, C#

done

done