• 0 Posts
  • 18 Comments
Joined 1 year ago
cake
Cake day: June 9th, 2023

help-circle




  • aaaantoine@lemmy.worldtoLinux@lemmy.ml*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    34
    ·
    10 months ago

    They’ve been separate desktop environments from the start. From top to bottom they share nearly nothing. The compositors, window managers, toolkits and shells are all different.

    They also are ideologically opposed. If they merged, which direction would they go? The more feature-rich KDE? Or the more streamlined Gnome? Such a merger would lead to infighting and stagnation.

    This is before even talking about the actual code underlying both environments.

    I think it’s better for everyone if they stay as two separate projects.











  • I feel like vanilla GNOME is intentionally a barbones common workflow, and that extensions are how you customize to fit your needs.

    For example, I often switch between desktop speakers and headphones (where the dongle is always connected), and sometimes other audio devices. I installed the sound input/output chooser so I don’t have to go into Settings every time I need to switch inputs. It saves me multiple clicks. But I get that not everyone needs immediate access to change audio devices, so why clutter the UI?

    I’ve used both vanilla GNOME and the post-Unity Ubuntu spin on it. In either case I’ve grown accustomed to the Activities screen, quickly accessing it pressing the Super key, and using it to switch windows and manage full screen apps on different monitors.



  • If the size of the PR is a concern, maybe the maintainers will allow a staged approach. Create an Issue describing the feature and indicate step by step how you would implement. Then break the work into multiple pull requests.

    If necessary, you could introduce a toggle that’s switched off by default until the feature is fully implemented.