That's not exactly true. On Linux, it's a real shit show because only KDE (Qt) supports proper fractional scaling, GTK apps don't. GTK supports 100%, 200%, and so on. You can play with xrandr, but that'll cause serious other issues (not even speaking about multi-monitor setups).
On Win10, however, all of the programs I'm using have flawless hidpi support - browsers, IntelliJ, console windows (cmder), Spotify, etc. W10 supports per-display DPI as well.
I don't know which applications are "crashing", that sounds like FUD. I know about two notable exceptions that don't have good hidpi support: Adobe tools and Hyper-V.
I'm not sure what "not exactly true" means, it's my personal experience of trying to run Windows 10 on my MBP. Many of the video tools I use regularly (for encoding, subtitle creation and editing, authoring, muxing, etc) are either broken or look bad. I understand that may not be mainstream use, but it certainly isn't esoteric either. You say browsers, but last I remember, Chrome didn't really support it. Now I am on Firefox, so it's proper, but that's not what most people use. Adobe software, as you said, is notorious at supporting scale. That's not esoteric either.
Chrome's hidpi support has been acceptable on Windows since about 2015. It's still not absolutely perfect (there are issues with 1px black bars when resizing Windows), but it's completely usable.
On Win10, however, all of the programs I'm using have flawless hidpi support - browsers, IntelliJ, console windows (cmder), Spotify, etc. W10 supports per-display DPI as well.
I don't know which applications are "crashing", that sounds like FUD. I know about two notable exceptions that don't have good hidpi support: Adobe tools and Hyper-V.