Even Android maps "1dp" to a non-integer number of pixels on most displays.
It looks "perfect" because of a combination of anti-aliasing and high density. But zoom in on a repeating pattern of 1dp lines, and you will see that some are aliased and some are not if your display's density is not an integer multiple of 160dpi (mdpi).
But Android can do this everywhere because everything draws to a Skia canvas under the hood (well, HWComposer/SurfaceFlinger, but basically Skia). Desktop operating systems don't have the same luxury. MacOS and Gnome render at 2x and downscale the entire frame, which produces decent results on high-density displays but look blurry otherwise. I have no idea what Windows does but it sounds like it's a mess.
It looks "perfect" because of a combination of anti-aliasing and high density. But zoom in on a repeating pattern of 1dp lines, and you will see that some are aliased and some are not if your display's density is not an integer multiple of 160dpi (mdpi).
But Android can do this everywhere because everything draws to a Skia canvas under the hood (well, HWComposer/SurfaceFlinger, but basically Skia). Desktop operating systems don't have the same luxury. MacOS and Gnome render at 2x and downscale the entire frame, which produces decent results on high-density displays but look blurry otherwise. I have no idea what Windows does but it sounds like it's a mess.