3 ms·
The problem is that there are no external 2x displays on the market (apart from the recalled trainwreck that was LG ultrasharp 5k): https://bjango.com/articles/
by baxuz 8y ago
The problem is that there are no external 2x displays on the market (apart from the recalled trainwreck that was LG ultrasharp 5k): https://bjango.com/articles/macexternaldisplays/ https://bjango.com/articles/macexternaldisplays/
Scaling is horrible on MacOS since it basically bumps up the 1x resolution to the next integer multiplier and then does a per-frame raster resize leading to performance drops, blurry edges and other render artifacts.
Meaning that your only reasonable option was to run a 1x monitor without scaling. Now they killed that option too.
Basically what they did, if your primary work machine was a MacBook hooked to a 27" display — is tell you "Buy an iMac and use Continuity".
I mean, I'm all up for removing subpixel antialiasing at the point where everyone is running a 220+ppi monitor. However, we're not at that point yet.
This is a horrible move that may cause me to drop the Mac as a development platform, since I'm looking at text for 8+ hours a day, and I'm not planning on shelling out 3k€ for an iMac or 2k€+ if they get back into the display business, just to fix something that they broke.
- ricardobeat 8y agoI use a display in the 'red zone' described in the article (a Dell P2415) daily paired to a retina MBP; there are no issues coming from not being an even multiple, it's the sharpest monitor I've ever had.
- baxuz 8y agoI recently worked on a 4k 24" monitor (~180ppi) on a 2017 MBP. The text was either too small when rendered at 1x, or the framerate dropped to a crawl when using a scaling option. Everything was rendering at under 60 fps. Plus I could clearly see the rendering artifacts when scrolling, mentioned in the article.