If it's fairly easy, then I think it still fits the spirit of the rules. KISS and all.
On the other hand, the idea that one might be setting traps is slightly weird... if you _know_ 90% that n will be large then pick an algorithm that's efficient (and since it's easy to implement, it's a win-win). If n is always going to be small, then does the choice really matter?
Yeah I agree with this. They cite the typescript compiler, which in addition to supporting .d.ts files also supports compiling regular JS in additon to separate TS files in the same project. I think this would have been a better approach for backward compat as well, so that users could upgrade to versions szupporting static typing and incrementally change projects one file at a time (leaving existing code intact).
Regarding the web, using a moderately sized column for the primary text (with a CSS max-width set for responsiveness) is generally a good idea, because humans are supposedly better at reading lines that arent too long. In practice, however, this doesnt always seem to be the case. Consider wikipedias regular website for example.
On the other hand, the idea that one might be setting traps is slightly weird... if you _know_ 90% that n will be large then pick an algorithm that's efficient (and since it's easy to implement, it's a win-win). If n is always going to be small, then does the choice really matter?