Hacker News Reader

I think you are almost be definition trolling when you write beating X (millions lines of code) with 600 lines.

because when you say 'beating' the implication is it does what X does better - as opposed to just matching my use case with 600 lines and not big dependency import.

this usage of beating is going to rile up (i.e troll) everyone familiar with the subject who can see thousands of ways you did not beat it.

View on HN

The funny thing is that the benchmarks that he wrote are more problematic than the T-WAND code itself.

He didn't use any benchmarking library, and he used System.currentTimeMillis instead of the high precision timer available with System.nanoTime.

He also instantiated the IndexSearcher without specifying any executor and he instantiated the legacy query parser on every lucene search

I think the heading is fine. They are beating Lucene in the context of their particular problem.

Any additional features that a product has but which you don’t need for a particular purpose is a downside, not an upside.

They’re not claiming to beat Lucene for the general case of everything Lucene is capable of.

He is beating lucene only if you look at his broken benchmark

Send a PR if you feel the benchmark can be improved. I will be happy to merge it and rerun the benchmark.

Reply on news.ycombinator.com