Hacker News Reader

Comment by deno | Hacker News Reader

VSCode works just fine with hidpi on Linux. It’s just an Electron app after all, and Chromium has had hidpi support since forever.

View on HN

Many many many apps on Linux still have massive issues with DPI, especially with mixed-DPI environments (which are no longer an edge case, they're the Common Case with a laptop attached to a monitor).

Even accessing machines remotely via Xrdp has huge issues because once you create the session with a certain DPI, logging into the session from a different DPI machine means you're stuck reading either extremely tiny or extremely huge text

Using mixed-blurriness environment sounds like a nightmare to me, even if everything should work correctly.

Its really not, only Linux makes it that way. If its done right (as it is on mac, and to a _very_ slightly lesser extent, Windows) there isn't 'blurriness' at all. One monitor will just happen to be sharper than the other.

I work every day with a 4K monitor and a 1080p monitor side-by-side and it works well. Linux couldn't handle it in any configuration, especially with mixed Intel integrated+nvidia graphics, but Windows is a champ.

Wayland+Intel is working quite well in my mixed 4K+1080p setup. Qt apps are handling like a champion. Gtk seems okay too.

Obviously it's not so great with Xwayland, definite blurriness there. But to compare, the only workable X11 setup was one that ignored my 4K screen entirely and the whole thing was blurry.

They are totally an edge case. If you care about hidpi why do you still have a bad external screen? If you don't care about hidpi simply set a lower resolution on the one hidpi screen.

Because that is a standard office configuration during the last 15 years, laptops with docking stations and external monitors.

More than enough time to catch up.

Yes, standard configuration where the laptop and the external monitor have about the same ppi.

? there's an enormous effort to fix the blurry chromium on wayland (and by extension electron and vscode), codenamed ozone, and vscode make me painfully aware of it every day.

Afaik there's no official vscode build on ozone.

https://bugs.chromium.org/p/chromium/issues/detail?id=578890

That’s an effort to have Chromium work natively on Wayland. It works just fine on X.org and even under Wayland with XWayland if you use something like ChromeOS’s Sommelier or just set window.zoomLevel/--force-dpi-something=2 (and not have XWayland windows scaled).

Reply on news.ycombinator.com