Hacker News Reader

You have the wrong end of the stick. The author means that he's ported it to achieve better performance than using Javascript's built-in map/filter./etc. operators because those do not lazy-evaluate and do not chain together efficiently, creating an array at each invocation.

I think word "performance" is not proper here. Maybe productivity.

I haven't looked into it yet but I see quite a few projects thinking they can outsmart the big boys by tuning for either extremely specific use cases or very small benchmarks.

The bigger argument against JavaScript in my view is the way the language is so antithetical to every lesson you'd have thought the industry has learned - even Go is safer than JS and Go is designed like it's from the 70s