> I think that laptops are not good for development. They are great in mobility and convenience, and this argument might outweigh everything else for some people. I accept that. But still, a desktop monitor + external keyboard are always better than a laptop. There might be other reasons for not buying a monitor, but having one, I hope, no one would argue it’s a superior dev environment.
100%! If you look at the image below this statement, the ergonomic disaster of craning your neck down to view the screen ("tech neck") is another reason to use monitors instead of laptops.
Unfortunately, and somewhat ironically, the 4K monitors the author recommends are not good for macOS due to them not supporting native retina scaling above 1080p. The only monitors that do are 5K displays, but neither of them can do 120Hz.
The prices for monitors with the features described in the piece have come significantly down from when it was written. You can get a very decent 4K@144hz monitor for around $650 USD.
> Because the only way to get good letters is by spending more pixels per letter.
> Because TODAY the only way to get good letters is by spending more pixels per letter.
There. Fixed.
All the bad examples given have antialiasing applied.
In the past there were bitmap fonts that were redered without antialiasing and they were very sharp (as sharp as a CRT could draw them) and then there was manual font hinting with no size interpolation and again with no antialiasing.
Today we can choose between antialiased fonts that are blurry, or no antialiasing that are sharp, but with ugly random stroke widths.
That's because today, who would spend a year to manually do font hinting on thousands of unicode glyphs and dosens of font sizes? And who would deny the user's "right" to footgun their eyes with a 12.5 font size on a bitmap font that only has sizes 11 and 13px?
Want some proof? Open the devtools on his blog and remove the unhinted "IBM Plex Sans". See how much better it looks with the old Arial instead.
The old fonts that have been designed as bitmap fonts or as scalable fonts, but with good manual hinting (which is equivalent with designing bitmap font variants for a set of usual sizes), can indeed be perfectly sharp.
Nevertheless, such fonts are always uglier than the good fonts which are rendered on a high-resolution display, where more pixels per character cell are available.
Even the 4k displays, when at typical desktop sizes and viewing distances, have a significantly lower resolution than what has been provided by the traditional printing of books on paper and than what is needed to exceed the resolution of normal human vision.
I do not consider any display that is uglier than a printed book from a few centuries ago as an acceptable display.
I accept your choice. Buy whatever monitor you like.
It would be good if programmers like that guy would accept MY choice and not force antialiasing on my eyes, and then blame the monitor instead of the font and the rendering engine.
DP 2.1 is arriving with ludicrous amounts of bandwidth (up to 80gbit/sec!) but it brings a new set of problems, copper cables rated to carry the full bandwidth are limited to about 1 meter. To go any further than that you will need some kind of active cable which don't exist yet. Moving that much data is hard.
4k (1080) is just way too small for me. I don’t see that many 5k or 6k options for a reasonable price. What is a nice setup for a developer? Go with 2x4k screens and you’re looking at bezels dead ahead, 3x4k and you’ll have to move your head a lot, or 1x6k?
I'm not sure what you mean by 4k(1080), but... I have an LG 38WN95C-W Ultrawide [0]. It's great for coding, great for video (IPS LCD so obv not deep OLED blacks), great for games...
3840x1600 resolution, which is roughly 3/4 of 4K cut horizontally.
By 4K (1080) I meant that a 4K screen has a typical resolution of 3840x2160, which gives you at 2x scale factor an equivalent screen estate as a 1920x1080. That's too little screen estate for me.
The screen you referenced would be even less than that at 2x scaling factor: 1920x900, which is even fewer screen estate.
A 4k ultrawide is not retina, so doesn’t cut it.
I can just get the whole width in my lateral field of vision, but I really need to move my head slightly to gain sharp visual focus all over the screen.
Wit a vertical 'resolution' of 2160, it gives me lots of lines of text.
"barely moving texts" ?
You must not be aware that, to render the cursor, the whole "surface" of the monitor is rendered.
They call this: "progress". /s
100%! If you look at the image below this statement, the ergonomic disaster of craning your neck down to view the screen ("tech neck") is another reason to use monitors instead of laptops.
Unfortunately, and somewhat ironically, the 4K monitors the author recommends are not good for macOS due to them not supporting native retina scaling above 1080p. The only monitors that do are 5K displays, but neither of them can do 120Hz.