I have been using sway on Fedora for a year. It's been really good so. It's a smaller niche than X.org's, but I get to do everything I need. HiDPI support is just right, just throw output eDP1-1 scale 2 in the config and you're set.
Clipboard works perfectly splendid, screen-sharing works (not as perfectly splendid as clipboard does), input works, chromium/electron is getting support for native wayland. Qt and GTK Wayland support's quite good.
I have had no problems whatsoever and I invite you to try it. I have no hard-proof evidence or numbers to support my opinion, just try it.
This is sway, i3 on wayland, a tilling window manager. Not some commercial piece of software that has to target the lowest common denominator to survive in the market. It's meant so that you configure it and it's very configurable. So it doesn't any defaults bar what's needed to launch the manager. The rest is up to you.
Configurability is great, but that isn't an excuse for having poor defaults. A child comment to yours mentions that Sway now uses a heuristic to find a "reasonable" default scaling factor, so it appears that Sway currently does the right thing.
The "standard" for anything today should be the physical display size divided by the pixel count to give the exact resolution for X and Y in DPI. Scaling should be relative to that physically correct resolution.
We've inherited a lot of baggage and odd conventions, some of which were wrong to begin with. I don't think we should be carrying on with it if we can do better. Having these scaling factors directly correspond to physical reality would be a start.
I'd rather just have the configuration file be simple and well documented and let me make the decision. My monitor running at maximum resolution is about 163 DPI, so an automated system could guess both ways. 200% scaling works well for me, and it's a single line of configuration, done once, and I don't have to worry about heuristics changing behind my back.
Why do you think it needs any of that? For that matter why do you think windows, mac, android, chromeOS etc. all need "explicit configuration"? They all simply set a reasonable default scale and then give you an easy way to pick a different one if you want.
Just out of curiosity, how does screenshare work for you? I've been trying setting it up for work (slack/teams), but to this day it just doesn't work. Using debian sid, so pretty up-to date packages tbh.
I just start new xorg session for screenshare, which, frankly, sucks.
Well, it works on FF and certain builds of chromium (those built with ENABLE_PIPEWIRE flag on). I am using xdg-desktop-portal-wlr and it works quite good. I was able to present my desktop to others without significant hiccups. Once Electron enables Ozone (and builds with PIPEWIRE on) we will be able to use screen sharing also on teams and other electron-packaged apps. This obviously works for my workflow and I understand it won't work for everyone. I don't know about Zoom, but I heard (and thus not entirely sure) it works only on specific distros with some specific GNOME versions.
Yup, this is sort of here with pipewire at this point, but it hasn't propagated through to the electron apps.
Slack is still a pain point for me as well, but mainly because Slack continues to demand that I install the desktop app for calls/screen sharing.
Zoom's desktop app also doesn't work, but I can use zoom-redirector and have the calls immediately open in my browser (you can get the same thing without the extension, but it requires you pretend that you can't install their desktop app and several button presses for every meeting).
My guess is that we're about 12 months away from having it work by default in most places.
The Electron apps are not there yet. I too have to use Slack ATM and my workaround is too have Pipewire working with Browser (Chromium and Firefox in my case) and use Slack in the Browser when I need to share my screen. If the target you want to share is a X window, you won't even need Pipewire since WebRTC will just work without it.
Clipboard works perfectly splendid, screen-sharing works (not as perfectly splendid as clipboard does), input works, chromium/electron is getting support for native wayland. Qt and GTK Wayland support's quite good.
I have had no problems whatsoever and I invite you to try it. I have no hard-proof evidence or numbers to support my opinion, just try it.