This would eliminate the alternative solutions like those that may be performing various text distance calculations against a known database of Jaden Smith quotes--although, unfortunately, many language variations of this kata have test cases which include random tests and assume the answer must be uniform based on criteria that has never been formally defined by Jaden Smith.

Sorry, forgot to mark I was responding to @Smcgb.

Also, @1axcoder, there are many approaches, the test cases are supposd to be easy to pass with a simple solution, and maybe you can revisit this kata after exploring other kata that manipulate text data.

I just added a lead-in sentence "Your objective with this kata is to implement an interpreter for the Whitespace language using the following description as a guide." Does this help?

Practice and also being able to review and understand other people's solutions. The less compact solutions aren't necessarily better or worse--they provide more detail into the underlying logical structure of the solution, whereas the more compact solutions take advantage of abstractions of the underlying logical structure of the solution--which may or may not perform better.

It's there because I find that it's reflective of real-world scope considerations where shortcuts that don't follow the original definition are liable to fail, particularly when working with Unicode. Would you be able to provide feedback on the definition specifically?

Edit to add, I think that working with date/time formats is the best example of what you're describing--while Unicode encoding variants are pretty much across the board, you-need-to-assume a Unicode encoding instead of say ASCII, Latin-1, or what-have-you these days.

Thanks! Never knew about that. I'm probably a repeat offender.

Wait, you can read solution comments without access to the solutions?

One of the original purposes of this kata was to provide light exposure to prototypal inheritance in Javascript.

The JS bootcamps likely stopped teaching this after ES6 came out, so I guess this is now a looking things up for yourself instead of being told exercise. TO NOTE: contexts of keywords and "prototype".

@darymc, just sleep on it. You're not missing the part of it I'm talking about, but the people you're responding to have.

I actually suggested that to the author to be consistent with the input/output capabilities of the original implementation. Makes me wonder whether there could be more done on the more modern Node.JS implementations.

You've misread the spec for stn.

Katakana uses multi-byte characters in UTF-8.

What solution are you referring to? Remember to mark as spolier.

The former is any character. The latter is any character that isn't EOL.