Stupid microoptimisations. Not only one should never optimize prematurely, and that is noted in the slides, but one should also never optimize like that (at least in the JS context). The interpreters/compilers/whatever will evolve for the readable cases, not for obscure idiocies, and programs using these techniques today will just run slower tomorrow.
HN user
xilun
What is the relationship between copyright infringement and Open Source???
Is it a sort of oxymoron exercise or something?
And do you think that _just_ knowing every function that already exists and how to use it would you make an expert ???
A little more productive maybe, but this is indeed neither a necessary nor a sufficient condition to be called an expert.
Higher levels considerations are far more important.
The real problem with the author of the initial post was that not only he had an "attitude", but he even was technically quite incorrect (he could have done worse, but still...), and not just once!
The collision fundamental misunderstanding was really not forgivable :/
Had he been technically correct, the whole non-stop "your question is really too imprecise" thing and perhaps even maybe the stinky "oh my God, the interviewer does not even know the XORBLUB algorithm" one would be more tolerable. But in the context of his own report of the interview, he is just pedant and not that smart...