Maybe PikaOS?
But, IIRC, they are not innovative like CachyOS is; CachyOS actually tries to push performance enhancements forward. PikaOS, on the other hand, only implements the improvements found by others (like CachyOS).
Maybe PikaOS?
But, IIRC, they are not innovative like CachyOS is; CachyOS actually tries to push performance enhancements forward. PikaOS, on the other hand, only implements the improvements found by others (like CachyOS).
deleted by creator
Don’t go straight to immutable Linux.
My first foray into Linux was through what you’d refer to as immutable Linux; shortly after the release of Fedora Kinoite. I’m literally the embodiment of the antithesis to your statement.
It is very new
This is factually true. So I can’t simply deny that. But being more precise is helpful:
and I don’t like the focus.
Could you be more elaborate 😜?
First step: Decide on the so-called desktop environment. A shortlist is provided below. For a new user, this should be decisive when choosing between beginner-friendly distros.
Before going over to the next (and final) step, we need to set the stage for our contenders:
Final step: Pick the distro corresponding to your preferred desktop environment. The list found below (ordered alphabetically) isn’t trying to be exhaustive on desktop environments.
Thank you for the kind words 😊!
Though, in retrospect, I hope the recommendation for Linux Mint works out for their issues regarding ACPI power states. Perhaps a bigger departure from Ubuntu (if at all) would have been beneficial here.
My go to back in The Day was just Ubuntu because I was lazy.
So we have a bias towards Debian-based distros.
it’s not been playing nice with my Zen 4 desktop when it comes to ACPI power states (no sleep, doesn’t reliably turn the power off when i ask it to turn off, etc).
However, a newer kernel is definitely preferred.
is also something based on a normal distro that most people write guides for because I am a smoothbrain.
And finally, healthy access to documentation.
Based on the above, I would not pick:
Let’s get to the actual recommendation, Linux Mint seems to be tailor-made for your use case:
Is there a specific android app you need?
Currently, there are already a couple I need beyond future-proofing.
https://gitlab.com/android_translation_layer/android_translation_layer/
Thanks for mentioning this! While I’ve had some experience with Waydroid in the past, this is completely new to me. Looking at it briefly, it seems to operate differently than Waydroid’s full Android emulation approach. Instead, it works as a translation layer (like Wine), making it both more efficient and potentially better integrated with Linux. Is this a correct assessment?
Despite having researched Android on Linux solutions before, I hadn’t come across this one. Typically, these discussions only mention Anbox or Waydroid.
Thank you! Much appreciated!
Thank you for chiming in and providing some much needed insight!
Is what you’ve described easy enough to accomplish for everyone with some Linux experience? Or do you think a guide of sorts is required?
Thank you for mentioning Jellyfin. However, unfortunately, I do need support for Android apps. That’s simply nonnegotiable. Mind you; I’m well aware of the capabilities of Jellyfin. But there are simply things it can’t do…
That’s actually pretty interesting. Thank you for mentioning!
Have you got any experience with this (particular) combination?
Thank you for the reply! And apologies for the late response*.
First of all, I owe you another apology for the deleted comment; I was still in the process of cooking and accidentally sent the undercooked message.
As per its README (I’m paraphrasing):
Bazzite started as a project to resolve some of the issues that plague SteamOS:
Like, SteamOS is a pretty cool operating system that allows both Linux enthusiasts and Linux newbs to enjoy playing (most of) their favorite games on Linux. But the former may find it too restrictive, while the latter may want to import that experience over to other devices. Bazzite aims to be that solution. Were it not for the success of the Steam Deck (and by extension SteamOS), such pressing need wouldn’t even have arisen. So Bazzite isn’t trying to target gamers as “an easy way to attract users” (or whatever the insinuation may be); its raison d’être is to address SteamOS’ limitations.
Regarding the targeting of programmers, you could be right on that. But I suppose it’s fine as VS Code’s inclusion (and other goodies) is only confined to the respective
-dx
images. I regard Bluefin (and Aurora; its KDE Plasma spin-off) as the opinionated distro its maintainers like to use for themselves (i.e. programmers). I’d argue this actually makes it suitable for most people. But your average Linux user is a lot more sensitive towards ‘bloat’. So it’s definitely not for everyone.I guess my reply would be that I simply don’t feel that way. And factually, it’s being worked on by people that work (or have worked) at places like Canonical, Red Hat and (even) Microsoft. So, while that doesn’t necessarily dismiss them as being “young edgy”, it does make it easy to trust and be confident in their proficiency and competence. I wonder what other distros are maintained by such a star ensemble.
This is probably some meme or meta joke/reference I didn’t get. Please feel free to enlighten me.
I admitted to as such in my first comment. But, what if, instead of looking up questions in your favorite search engine, you visit their support channels and get the exact answer within a couple of moments? This last bit has been based on my own experience*.
Instinctively, I just absolutely have to disagree on this. The most clear-cut counterexample would be how NixOS -the granddaddy of
immutableatomic distros if you will- doesn’t adhere to many Linux conventions (including FHS). Therefore, “understanding (traditional) Linux under the hood” might have even been detrimental and wasteful for the many things you’d have to unlearn.Beyond the overlap in Linux 101 that most distros adhere to and/or the basics everyone should know about their operating system, could you please demonstrate how “understanding (traditional) Linux under the hood” becomes necessary with atomic distributions?