• 0 Posts
  • 33 Comments
Joined 1 year ago
cake
Cake day: July 23rd, 2023

help-circle


  • Why is that a gap worth filling? There is no benefit to users as long as its free of a EULA they don’t have to care either way. For those wanting to produce open source software based on same they already have all the rights they could need. The only party clamoring for permissively licensed software are companies intending to close off the source and sell other people’s work.

    I understand why they would want to do that I don’t understand why anyone would feel the need to work for free for something someone else closes off.






  • Building on top of wlroots is still a different scope of problem than writing a window manager for X. Pretending its the same thing doesn’t change the fundamentally different architecture even if it certainly makes it easier.

    Out of all the libraries isn’t recent KDE the only fucking one that supports proper scaling of xwayland windows without turning it into a blurry mess? KDE which nice as it is lacks most of the nice tiling features of i3wm or the per monitor workspaces? Let me rip out and throw away a highly functional Nvidia GPU and come on down!

    Don’t worry in another fucking 10 years all problems will be solved in the meanwhile I’ll just be fucking using non-beta software. Pardon me if I’m a little annoyed. Wayland has been the future for a while now.



  • X has a singular fully functional implementation into which you can slot a wide variety of components. Because everything is a component that slots into the singular X implementation forking has both a low benefit and a high cost.

    Wayland is just a protocol everyone must implement with a semi useless reference implementation that nobody would ever use. Nobody forks Wayland they just implement it as they must the X approach isn’t available.

    It’s apples to oranges. A meaningless comparison. Its more just churn than innovation on the part of desktops.






  • Nvidia appeared fairly buggy as of nvidia 535 and kernel 6.3 with both sway and Plasma 5.27. Notably of all the possible choices for Wayland support ONLY KDE in relatively recent releases supports proper scaling of apps using xwayland which are apt to be a thing for a while now. This is a huge point in KDE’s favor despite loving the idea of an i3 like experience with sway.

    If prior experience bears out plasma 6.0 will be buggy as fuck and 6.2 will be excellent.

    Nouveau has NEVER been a particularly good choice and its primary developer just resigned https://www.phoronix.com/news/Nouveau-Maintainer-Resigns I wouldn’t pin my hopes on it in the future becoming usable. I sure as hell wouldn’t say its a useful choice NOW because you suppose it may become so in the future. I’d rather look at nvidias official open source effort.

    If I had a crystal ball to look in I bet it would say a lot of folks with existing Nvidia hardware are best off sticking with X11 in 2023 but looking again at KDE’s wayland session in 2024.

    Although do bear in mind people using stable distros like Ubuntu/Mint/Debian will be a lot longer seeing new useful features pushed out.





  • There really isn’t any such thing as a “pure mate experience” for instance normal install likely contains VLC/Smplayer for multimedia, libre office for office docs, and firefox or chromium for web browsing. Not only are none of these mate apps most users probably spend most of their time using apps like these than their file manager.

    Then if you look at the other mate apps. Mate Terminal is hardly the best terminal nor is Atril the best pdf viewer. Kitty is a better terminal and zathura and Okular are both better PDF readers. Pluma is a mediocre text editor.

    The useful parts of an env are its settings menu, window manager, bar, and file manager. Pick one you like and then pick useful apps to go with it.


  • Nemo is the file manager for cinnamon. Dolphin is the file manager for plasma. Although they perform the same task their executables are on different paths as are their files. You could install 10,000 packages and never find a conflicting file save literal forks of the same project which your package manager will tell you about if you install both A an B. An example would be i3 a window manager, and i3-gaps a now depreciated fork of i3 which provides, you guessed it, gaps between windows.

    There is no reason to believe installing 17 different environments would conflict let alone 2. There is no need whatsoever to keep anything separate from one another nor is there any reason to believe one would interfere with another.