Quite a few people have remarked on the performance problems. For the spacing thing, the use of Adwaita doubled the minimum width of things like the Fill & Stroke panel because of its excessive button padding, so that on my Surface Book (effectively 1500×1000) with the typical layout, I would end up with something like a 35–40% reduction in available canvas width (and maybe 10–15% for the height); but even the common resolution of 1920×1080 is going to suffer a fairly significant reduction in available width, compared to the Win32 theme.

But I couldn’t even properly switch back to the Win32 theme because of severe bugs that rendered it very problematic on all displays and basically completely unusable after a bit on any comparatively small high-DPI displays like my Surface Book’s. I don’t know if any of these issues have been fixed; I did try Inkscape 1.0 final briefly but decided it was still just too bad compared to 0.92. And now I’m back on Linux and so, like the Inkscape developers, don’t care all that much about Windows any more.

(https://gitlab.com/inkscape/inbox/-/issues/879 was my initial report, including explanation of some of the major Win32 theme regressions. Given the adjacent topic in this thread of GTK 4, the mention of overlay scrollbars in that thread points to a mess too; https://wiki.archlinux.org/title/GTK#Disable_overlay_scrollb... says: “as of GTK 4, the overlay nature of the scrollbars is part of the toolkit.” Ugh, GTK is obviously not interested in being a native look-and-feel toolkit if they deliberately remove the ability to control scrollbar overlayedness at the system level or in the theme. If you require the app to switch it on, it might as well not exist. Sounds like they’re continuing with the sabotage.)