1. Current monitor
    1. HP L2245wg
    2. Old monitors
  2. Possible monitors
    1. Full gamut
    2. Normal
    3. Note on latency
  3. Mounts
  4. Resources

Monitors are devices that display information visually. They can include speakers and other connectors like USB. They were connected through VGA connectors for the long time, but that has generally been replaced by HDMI connectors, with a short period during which DVI connectors were produced. Resolutions vary too wildly wildly too mention here, see this article for details.

Now I'm buying a new laptop and would love to have an external monitor. I can afford something better than the one I have now, but it can't quite be 4k yet, according to this comment. The spec should be capped at "1440p at 60Hz", which I assume is 2560×1440 or QuadHD), which is already pretty good.

Current monitor

HP L2245wg

Upstream, manual, specs.

Old monitors

I somehow managed to collect a ridiculous pile of old monitors. Here's what works and doesn't, in descending order of (totally subjective) "quality":

Those monitors do not power up at all:

Possible monitors

See also this discussion:


See the selector: https://www.tftcentral.co.uk/selector.htm

Full gamut


Another idea: a USB C monitor

Note on latency

Latency might seem like a trivial concern for a non-gamer, but it actually matters. In their Typing with pleasure article, Pavel Fatin explains that even 1ms delays matter. In my terminal emulators review, I argue that we should follow the GNOME HIG that sets the bar at 10ms. Considering that my main work tool (Emacs) has a mean input latency of around 5ms, adding 5ms latency to the output, just through the monitor, is unacceptable.

So I'll set the bar, arbitrarily, at 2ms, but ideal this would be 1ms or below.

Keep in mind that the best total input latency for a computer is currently at 30, with the Apple IIe, according to Dan Luu. But that takes into account the entire processing cycle, which includes input, processing and output, if we adhere to Fatin's vocabulary. The benchmarks I performed in my blog post concern only the processing side of things, as we don't physically bash on the keyboard to generate those keypresses. In other words, assuming a 2ms latency in the monitor and 5ms in Emacs, what we actually have is:

Source Latency Notes
Input 14 ms Fatin, section 2.1, avergge
Emacs 5 ms Anarcat, section 1, rounded mean
Screen refresh 8 ms Fatin, section 2.3, average with 60Hz monitor
Pixel response 2 ms Assumption, above
Total 29 ms

So in theory, with a 2ms monitor and best conditions in Emacs, we should rival the Apple IIe input latency. In practice, considering Luu's results, it's very likely that I'm missing some numbers here and latency is actually much higher.

In any case, that's way beyond the 10ms objective, so it makes sense to reduce the monitor latency if possible. In fact, when looking at this, one has to wonder if the keyboard would be a better place to look for latency improvements. After all 7 ms spent in debouncing seems pretty horrible...


A friend recommends the VIVO STAND-V001JB. Unfortunately, it's hard to find and basically only available on Amazon in Canada. So here's a little shopping list while I'm there:


Created . Edited .