3 ms·
Remember "25000 string allocations per each key stroke"? https://groups.google.com/a/chromium.org/g/chromium-dev/c/EUqoIz2iFU4/m/kPZ5ZK0K3gEJ?pli=1 https://grou
by troupo 1y ago
Remember "25000 string allocations per each key stroke"? https://groups.google.com/a/chromium.org/g/chromium-dev/c/EUqoIz2iFU4/m/kPZ5ZK0K3gEJ?pli=1 https://groups.google.com/a/chromium.org/g/chromium-dev/c/EU...
- quietbritishjim 1y agoThat's certainly interesting but to give context for those not following the link: This is for entering into the address/search bar, so it covers all the work of searching history, performing network requests to autocomplete search terms, and displaying those results. It's not like entering a character into a regular text box on a page.
- troupo 1y agoIMO no amount of context can justify 25000 string allocations per key stroke :) Also, if you read the issues in the first post, it has nothing to do with "covering all the work". It's just really bad programming