| "but it's absolutely based on GNOME, the desktop stack. Just to clarify your clarification. :)" GNOME Shell is not the same as the rest of the stack. "Budgie can't even comfortably coexist with GNOME Shell on the same OS installation" Yes, it absolutely can. You can use GDM and log in to both. "If you change your settings in GNOME Shell with the Settings app, it will affect your Budgie session." It entirely depends on what settings you change. For displays, that generates the mutter related configurations which are used by Budgie because Budgie uses Mutter. Networking is related to NetworkManager and not GNOME. Notifications is something we intentionally hook into for filtering apps in Raven but can trivially be changed, we even have our own set of exclusions. Search doesn't apply to Budgie, that is specific to GNOME Shell. Applications is primarily oriented towards Flatpak. Most of the screen locker functionality isn't related because we use slick-greeter+lightdm+budgie-screensaver (a fork of gnome-screensaver). Sound can be independently managed, we do that via Raven for example (which ties into Gvc). Power settings leverage a mix of gnome-related settings and upower. Mouse settings are primarily related to libinput. I could go on. "Maybe you shouldn't say it's "based off of GNOME Shell", but it's probably accurate to say that Budgie is an alternative Shell for GNOME." Not really. There are many settings we expose which are not related to GNOME or GNOME Shell at all. "I even remember Solus devs at the time saying they might never actually do version 11 because they had fixed and worked around some of the issues that they thought they wouldn't be able to in 10.4(?)." Yes and then Ikey, the project founder, let and I took over in late Budgie 10.4 and my first release was Budgie 10.5. I went back and fixed issues that previously were implied to only be fixable in Budgie 11. "So, is Budgie 11 actually going to happen?" Yes however it is not a priority over other aspects of Solus development. |
> Yes, it absolutely can. You can use GDM and log in to both.
>> If you change your settings in GNOME Shell with the Settings app, it will affect your Budgie session.
> It entirely depends on what settings you change. For displays, that generates the mutter related configurations which are used by Budgie because Budgie uses Mutter. Networking is related to NetworkManager and not GNOME. Notifications is something we intentionally hook into for filtering apps in Raven but can trivially be changed, we even have our own set of exclusions. Search doesn't apply to Budgie, that is specific to GNOME Shell. Applications is primarily oriented towards Flatpak. Most of the screen locker functionality isn't related because we use slick-greeter+lightdm+budgie-screensaver (a fork of gnome-screensaver).
> Sound can be independently managed, we do that via Raven for example (which ties into Gvc). Power settings leverage a mix of gnome-related settings and upower. Mouse settings are primarily related to libinput. I could go on.
This is exactly my point. Of course you literally can install Budgie and GNOME Shell next to each other. But the very fact that they step on each others' toes is what I meant when I said "comfortably".
The fact that you basically have to guess what settings will affect the other DE is my point. It also happens to some extent with all DEs- you have to have an intuition for what settings are "system" settings and which are "desktop" settings. But I remember being frustrated in particular that some settings, especially with regard to Mutter, affected the other DE. Neither desktop's settings actually refer to Mutter explicitly, so how is a user supposed to know that changing the window decorations or the double-click-titlebar behavior is going to transfer? I also vaguely remember some settings being exposed in one DE's settings app, but not the other's, but that setting actually having an effect across both (likely Mutter and Gnome Tweaks, if I had to guess).
I'm just saying- I recommend not running both Budgie and GNOME Shell.