Correct

Thank you!

I was more worried on the cybersecurity side rather than the work allocation issue.

My apologies for the miscommunication; I wasn’t coming from ChromeOS, I was skating it as the only viable alternative, though undesirable.

Wayland has a ton of issues on Plasma including but not limited to (Not including NVIDIA Issues) (Note that many of these will be fixed in Plasma 6):

• Applications don’t prompt to save unsaved work, causing data loss
• No session restore for native Wayland windows
• When the compositor crashes or restarts, non-Qt apps are killed — work is ongoing to fix this
• Not all Sticky Keys options work
• No color management or support for changing Gamma
• KFontView is unable to open or install a font
• Session-restored windows go on the wrong screens and virtual desktops
• When dragging files, to trigger a specific result, you have to hold down a modifier key before you start dragging, not after
• Installed Chrome apps are grouped together with Chrome windows in Icon-Only Task Manager
• Global Menu is broken for non-Qt apps
• When using a Chromium-based browser in native Wayland mode, dragging an image to the desktop creates a sticky note out of it