Using keyup makes no sense and is inconsistent with user expectations. For triggering actions (which includes normal typing), you only ever use keydown. (Well, there’s one exception for reasons unclear to me: activating a button by pressing Space. That triggers on keyup like how clicks are on release, while Enter triggers on keydown.) Keyup is limited to things where you’re constantly reacting to the state of a key, as is common in games.
replyThis affects the functionality, too. It is in fact introducing latency by using keyup instead of keydown. Feels bad.
This autocomplete suggests domains that don't exist. You can just type garbage and it will suggest something, but then if you go there, there are no records.
replyIt seems like one purpose of an autocomplete box is help you avoid typos, so that makes it less useful.
If you’d like to reduce the network latency further you can store each trie node as a file, naming it conveniently the prefix path to that node. Then dump the few hundred million files onto R2.
replyNow the traversal can be done completely via CDN lookups!
Unfortunately this approach doesn't feel that great down here in Australia, definitely a function of latency.
replyI think you could get a lot closer by framing this as an optimization problem, where you use the full alphabet dictionary, but add a residual prediction which aims to cover as much of the remaining domain name tree as possible weighted by popularity. This tree could then be pre-baked and stored with the same system. This would probably get you p99 0ms even in Australia.
Clever but that’s not how we measure latency.
replydeleted
replyWhen it comes to UX, perceived latency is king.
replyThe perceived latency starts from keydown, not keyup. Redefining latency to start at keyup reduces measured latency, not perceived latency, and delaying the visual display to keyup makes perceived latency strictly worse, not better. Even sticking with the keyup definition, just displaying the result as soon as it is available gives the possibility of negative (defined) latency.
replyI think you don't fully understand. They aren't just doing a search based on the key being pressed down. They already did a search based on the previous characters that returned results for all possible next characters. So by the time you type a second character it just checks results locally from the search that had likely already been returned from when you had typed the previous character.
replyThey do that, yet proceed to kneecap the perceived latency by delaying the render.
reply> And on keyUp (the user releases the key), we render the suggestions.
Autocomplete aside, this is a pretty nifty tool.
replyPretty sure we mean < 1ms rather than actually instantaneous.
replyOn a technical level yes but once you factor in monitor refresh rates then you can get to levels of optimization where it simply doesn't matter because you are constrained by waiting for the refresh rate anyways.
replyIts like tic tacs saying they are 0 calories because they got the per serving size down low enough to round to 0.
replyLooks more like 500ms?
replyits pretty clever but what happns when someone pastes a domain or uses IME or voice input? the api being that fast is still impressive.
replyKeyDown events don’t work great for mobile, though.
reply[flagged]
reply