Submission timeline
2007–2026One slot for every year since HN launched. Height is that year's peak points; orange marks a 100+ point or 50+ comment breakout. Select a bar to open its strongest thread.
First comments on top threads
HN comment orderInteresting stuff. The article is quite verbose -- here is the Cliff Notes versions: The trie is a well-known data structure for storing string sets or string-keyed maps (https://en.wikipedia.org/wiki/Trie). You can compress a trie by using a DAG/FSM instead of a tree -- this lets you share states for suffixes, whereas trees only let you share states for prefixes. But for large sets minimizing a DAG is too expensive to perform on the whole trie. If you insert the keys…
The FST mechanism for using an acyclic graph to store information is very reminiscent of GADDAG[1] structure for Scrabble dictionaries. In my search for interesting problems in the compression space, I ran into quite a lot of genomics research which suggests combining a compression algorithm with a lookup method, because identifying common items between samples reduces both storage and speeds up lookup. > An FST based data structure as presented in this article does not have this capability. Namely, once…
This is the same individual who spent over two years writing a faster grep than grep: http://blog.burntsushi.net/ripgrep/ Amazing work.
(with proper formatting this time) Note that it is perfectly possible to have more complicated values associated with FST keys, just not in the https://docs.rs/fst/0.3.3/fst/map/index.html implementation. FST's can also be cyclic – this lets you represent things you couldn't with just a hash table. ----- Anyone who wants to play around with this should try the HFST[1] library, which lets you create compact and possibly cyclic string-to-string maps, which are closed under union, intersection, reversal, inversion…
The first top-level comment from each of the four biggest threads, in HN’s own order. Excerpts are shortened; open a comment for full context.
- Breakout years
- 2
- Total points
- 497
- Total comments
- 40
100+ points or 50+ comments
reference only — not used in Hall rules or ranking
reference only — not used in Hall rules or ranking
Every submission
| Date | Title as submitted | By | Points | Comments |
|---|---|---|---|---|
| 2015-11-12 | Finite state machines as data structure for representing ordered sets and mapsFirst breakout · Best thread | dbaupp | 213 | 25 |
| 2017-02-17 | Index 1.6B Keys with Automata and Rust (2015) | nanxor | 82 | 2 |
| 2018-09-08 | Index 1,600M Keys with Automata and Rust | tosh | 4 | 0 |
| 2018-11-11 | Index 1,600M Keys with Automata and Rust (2015) | jxub | 5 | 0 |
| 2018-12-17 | Finite state machines as data structures (2015) | heydenberk | 8 | 3 |
| 2019-11-23 | Index 1.6B Keys with Automata and Rust (2015) | pkilgore | 3 | 0 |
| 2021-08-16 | Index 1,600M Keys with Automata and Rust | redman25 | 3 | 0 |
| 2021-08-20 | Index 1.6B Keys with Automata and Rust (2015)Latest 20+ point return | ithkuil | 174 | 10 |
| 2023-12-06 | Index 1,600M Keys with Automata and Rust (2015) | tosh | 2 | 0 |
| 2024-08-23 | Index 1,600M Keys with Automata and Rust(2015) | krelian | 2 | 0 |
| 2024-11-12 | Index 1,600M keys with finite state automata and Rust (2015) | fanf2 | 1 | 0 |
