[mech422]

Hmm - I'm not sure those sorts of things would require a fork per se, but I can see making it more familiar to windows/mac users could be a good thing. I was just curious as I was a big KDE fan back when I used Linux full time, and wondered what had changed.

The two biggest issues I'd have with Linux full time would be audio and video. I haven't even attempted to run Linux audio in like 5-10 years - it was always so titchy with multiple 'standards' to configure. Video was not quite as bad, as I don't game much so I just needed basic functionality. But now I have multiple 4k monitors, high dpi, and all that jazz, I don't know how big a pain it would be. I just run linux in VMs (standard device drivers and setup) or ssh into a linux server for now.

[jwells89]

A fork wouldn't be explicitly required, but generally in established FOSS projects, when attempting to make changes that are either large or widely peppered throughout the project you're going to be fighting against headwinds from people who are happy with project as it is, which is understandable. You're likely going to find yourself spending more time on negotiating and politicking to get changes committed than actually making changes.

Audio/video has more to do the distribution being used than it does one's desktop environment, though the DEs can do things to smartly design configuration UI and surface the most commonly used A/V settings in the right places.