|
|
|
|
|
by martin_dd
749 days ago
|
|
Author here. Yes, the search bar is nice already, and the performance is good enough for most use cases. Fun fact, javadoc's search is O(n), Docland uses binary search so it's O(log2n). That's why the search bar in the official java.base documentation is noticeably laggy. The real benefit of customizing search is custom ranking and filtering logic. Docland sorts the search results by relevance (matching prefix length and casing) and dedupes overloads. In my (possibly biased) opinion it's easier to use. |
|
Agreed. If you do have performance improvements in mind, I would recommend you bring them up to the Javadoc jdk team. They would definitely take a look if you can point out a faster solution.
https://openjdk.org/projects/javadoc-next/
> That's why the search bar in the official java.base documentation is noticeably laggy.
On my $400 laptop from 2020, I have a response time of <= 0.25 seconds. Are you seeing something different?