Joshua Strobl, who was Experience Lead for the Solus Linux distribution, has officially quit but work on the Budgie desktop environment continues.
Announcing the departure on Twitter, Strobl linked to a longer statement that went over some rather vague issues that probably won't make much sense to anyone who isn't close to Strobl or the project. These include problems "which affect the ability to contribute to Solus, both from myself and others in the community".
The good news is the fancy Budgie desktop environment will live on as an independent project. Budgie now has a new home on GitHub, under the "Buddies of Budgie" organisation. Strobl mentioned the intention to invite developers from Ubuntu Budgie, Endeavour and more to contribute to it.
Solus itself will also continue on, with it being mentioned that the hand-over between Strobl and others will be "graceful".
This isn't the first major blow for Solus, since they also had to deal with the original creator Ikey Doherty quitting a few years ago. Seems like there's some wider problems they need to deal with if they're to keep Solus going. Strobl also mentioned a plan to join up with Doherty on SerpentOS.
Quoting: STiATWell, I can understand disliking that situation. But I like the choice of bypassing packages I don't need, so I'm glad Arch exists and is like that. For example, I don't need the Android support you do. Even Manjaro makes too many choices I don't want and have to undo. There are plenty of distros to choose from! Might be a hot mess based on your desires, but there must be plenty of people who see it differently.Quoting: 14Quoting: STiATWe'll see where this leads, but I do not have another disro providing an experience even close to Solus, so I'll stick with it (and I used Arch 2004-2017, tried it over the holidays again and it's just a mess).Sounds like the AUR is not for you. But I'm curious: why did you try Arch again over the holidays? And what's a mess anyways, the fact that you have to make more decisions as to what to install?
I do not want to manually search for depends when things don't work I do not want to fiddle around, I want a system/Desktop that just works.
The mess is that it does not come with sane defaults, as with dependencies.
For me, if an application requires dependencies to make functionalities work which otherwhise simply throw errors and nobody knows why - that's a bad decision not to have it as a dependency. Even if it does not require it at compile time. Arch disagrees on that opinion.
It's not about decisions to make, it's about if you install a package it will actually work properly or not. And in that regard, Arch is a hot mess.
An example would be: KDE, Dolphin requires kio-extras to be able to get android phones working. But wait, installing kio-extras it does not. Since you require an optional mtp lib. That done, on some devices, it will still not work. You need some udev rules package.
Otherwhise Dolphin will give some cryptic error. That's not exactly what I expect, if I install the kde meta package, that stuff should be included. Ye, there may be udev rules I do not need. But that's the point, Arch has the minimalistic approach making it basically a bad experience even if you use meta packages. Though, I think kio-extras by now made it into the meta depends.
See more from me