olivernn

6 ms·

1.
by olivernn 2y ago
Many years ago, when I was building Lunr, it was initially based on IndexedDB, but it was _much_ slower and the datasets I had in mind easily fit in memory so I didn’t pursue it. No idea if that has changed since though.
2.
ZSA Moonlander: A next-generation ergonomic keyboard(zsa.io)
202 points by olivernn 6y ago|275 comments
3.
by olivernn 9y ago
Using `charCodeAt()` for numeric keys is an interesting optimisation, I'm definitely going to try that out with Lunr.js. I'm also interested in _why_ that is quicker though, aren't all object keys converted to strings anyway?
4.
by olivernn 9y ago
Lunr.js [1] used to use a trie data structure and memory usage was a concern. The problem is that although the data structure compresses prefixes, it does nothing for suffixes. Depending on the corpus this can lead to a lot of duplication.
5.
by olivernn 11y ago
The last time this article was on HN I took a look at adding Okapi BM25 to lunr, from what I remember the changes don't seem to huge, its just a matter of getting the time to sit down and implement it!
6.
by olivernn 11y ago
I'm fairly sure elastic lunr is a fork of lunr, I still seem to have the most commits even! [1] I'll have to take a look and see what @weixsong added, perhaps there are some changes that I can merge upstream. [1] https:/&#x2
7.
by olivernn 11y ago
I've come across these two: * http://reyesr.github.io/fullproof/ * http://www.tipue.com/search/ Might be interesting to see how these also stack up.
8.
by olivernn 11y ago
Nice. It'd be interesting to see the comparative performance of the three libraries under test, e.g. time to results and possibly memory usage.
9.
by olivernn 13y ago
Who'd have thought the most English looking location would be in Wales ;)
10.
Building A Full-Text Index In Javascript(garysieling.com)
70 points by olivernn 13y ago|11 comments
11.
by olivernn 14y ago
Why is it a red flag for a browser-based javascript library to require a browser for testing?
12.
by olivernn 14y ago
That is almost exactly what lunr is doing. It tokenises the input text, stems the tokens and filters out any stop words. The index it can be searched, the order is not relevant, a prefix search is currently used so that you can find documen
13.
by olivernn 14y ago
Since the library can be run outside of the browser (using node.js for example) the index could be generated server side, and then just passed to the client. I hadn't considered this before but it might be worth looking at.
14.
by olivernn 14y ago
The example ( http://lunrjs.com/example/ ) indexes 100 stackoverflow questions, some of which are relatively long. If indexing performance starts to become an issue the whole search index can be moved into a web-worker, which prevents index
15.
Building a full-text search engine in your browser(blog.new-bamboo.co.uk)
5 points by olivernn 14y ago|0 comments
16.
Show HN: UK Weather Visualisation(uk.temperature.at)
22 points by olivernn 14y ago|2 comments
17.
Experiments with the HTML5 Audio Data API(blog.new-bamboo.co.uk)
1 points by olivernn 15y ago|0 comments
18.
by olivernn 15y ago
I have a similar library here http://bit.ly/fTj2Ls that uses pushState to provide a routing layer so you can handle perform ajax (or anything else you want to do) when a link is clicked. The best bit is that if JavaScript, or pushState,
19.
Degradable JavaScript Applications Using HTML5 pushState(blog.new-bamboo.co.uk)
2 points by olivernn 16y ago|0 comments