HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
pavelfatin
typometer
Java2017–2022
pavelfatin / typometer

typometer

Text / code editor typing latency analyzer

Developer Tools
Explore on GitHubRead Hacker News discussions
6Distinct people
6Mentions
0Explicit recommenders
403GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Text / code editor typing latency analyzer

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year6 dated mentions

Observed mentions: 2017-07-19 06:19:43 UTC to 2022-05-24 18:12:38 UTC.

0122017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2022

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC202
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC202
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC202

What Hacker News says

6 sources
qiller·May 24, 2022
There is a great comparison between various terminals' latency https://danluu.com/term-latency/ (it comes up periodically on HN too - https://news.ycombinator.com/item?id=19443076), so once when I was curious if it was just me or if RDP was indeed slower, I did a quick test using the same toolset - https://github.com/pavelfatin/typometer It is not a super-scientific test since: 0) I didn't spend too much time on this 1) I wasn't able to test Sublime Text or VSCode over RDP as the tool would stop "typing" after a few characters 2) I did test Visual Studio 2022 though - since this is the primary reason of why I even have a remote Windows box 3) When running on M1 mac, Java can't seem to use native APIs for screen capture, so I'm not sure how much that affects the results Parameters: 1) Remote - Windows 11, hard-wired LAN, running in 4K usin
Read the rest
g an HDMI emulator plug 2) Local - MacBook Pro M1 Max, over wifi (speed test around 400mbps) 3) Using the official RDP mac app 4) Using Retina mode, True color when connecting (essentially making a 4K HIDPI connection, just checked right now using https://whatismyviewport.com/ - Chrome gives 2560x1339px screen size with DPR 2.0) Testing typometer on local (Mac's) Sublime Text: Average latency: 20.9ms, SD 16.7ms Typometer running on the remote box itself, Sublime Text: Average: 51.7ms, SD 39.8ms Running on the remote box, testing Visual Studio 2022: Average: 62.7ms, SD 10.2ms And finally running VS2022 over RDP: Average: 216.9ms, SD 106.1ms So overall it is not VERY bad, but it is still very noticeable. For example, autocomplete/suggestions popups feel definitely laggy
In Microsoft Dev Box
ahub·Feb 4, 2022
Not sure if it's relevant but I liked the approach of Pavel Fatin in measuring editor latency [0]. It uses OS level input events and actual rendering on screen. So testing the same editor/file with different settings might yield results that are different depending on your scheduling config, while staying close to a "real world" example. He shared [1] the tool he made for the tests. I'd be curious to know your results regardless of the technique used. [0] https://pavelfatin.com/typing-with-pleasure/ [1] https://github.com/pavelfatin/typometer
In Ask HN: Is there any tool for benchmarking responsiveness for Linux?
IfOnlyYouKnew·Aug 1, 2019
Here's some comparison of input lag: # Title Min Max *Avg* SD 1 iTerm 3.3.0beta16 11.2 33.6 15.9 3.4 2 iTerm 3.2.9 10.8 29.5 21.3 4.5 3 hyper 3.0.2 22.3 46.9 27.6 3.6 4 Terminal 2.9.1 2.4 8.3 5.8 0.5 5 Alacritty 0.3.3 5.2 16.8 6.3 1.4 6 Kitty 0.14.3 7.7 11.6 9.6 0.8 Measured using https://github.com/pavelfatin/typometer Edit: Added iTerm 3.2.9 (2) added alacritty (3) added Kitty
In iTerm2 3.3

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.