Farewell, macOS

Re:Farewell, macOS by chrismorgan on Monday November 16, 2020 @07:22AM (#25110779)

> I was positively surprised that Ubuntu picked up the native resolutions of both displays

This makes me curious, because I on the other hand would be astonished if it didn’t pick up the native resolution of all displays. So I’m interested in what the mental model is that leads to being surprised when it does work—I know there’s plenty of stuff that I don’t know how it works and may guess incorrectly! As it stands, the only sort of mental model that I can think of is the screen telling the OS “I’m a such-and-such type of display and my resolution is so-and-so”, either when you plug the device in or when the OS asks.

[ Parent | on HN ]

Re:Farewell, macOS by Symbiote on Monday November 16, 2020 @07:29AM (#25110841)

There's a tool to show the EDID [1] information.

  $ sudo apt install read-edid
  $ sudo get-edid | parse-edid
  ...
  Modeline        "Mode 0" 594.00 3840 4016 4104 4400 2160 2168 2178 2250 +hsync +vsync
  ...

Perhaps the mental model comes from using Windows? I don't know what combination of hardware, dongles, docks and monitors causes it, but some of my non-technical colleagues end up with their monitors in non-native resolutions with Windows 10.

[1] https://en.wikipedia.org/wiki/Extended_Display_Identificatio...

[ Parent | on HN ]

Re:Farewell, macOS by chrismorgan on Monday November 16, 2020 @09:45AM (#25112234)

Hmm, yeah, I guess a long time ago some screens did tend to end up with the “generic plug-and-play monitor” driver and have it not know what the true resolution should be. I’d forgotten about that, not having seen it happen for at least ten years.

[ Parent | on HN ]