I feel like you'd love tldr.
SecondComingOfPheusie
joined 3 days ago
OP, I urge you to clarify and/or elaborate in case you desire better engagement. Like is your goal to make a long list of Wine-related software? Or, instead, understand which one is preferred?
Furthermore, a more meta suggestion: a quick glance at your profile shows that you have almost three times as many posts compared to your comments. You're free to engage however you wish. But please, consider engaging more with the community output. Thanks in advance!
Thank you!
- I can understand why the random long load-times for apps is very frustrating. I don't recall other Bazzite users complaining about it. So I don't know how widespread the problem is.
- I've effectively been on GNOME ever since I made the jump to Linux. So I can't comment on Dolphin.
- I can 100℅ relate to windows not restoring their prior states. I've used a tiling window manager extension on GNOME just because it handled that more gracefully; I like them maximized anyways.
- The audio sink thingy should have been available as a toggle by now. It's unfortunate that it seemingly hasn't. Though, I do wonder if pavucontrol would have been sufficient. There seems to be a flatpak for it if you're interested.
- The developer experience on Flatpak leaves a lot to be desired 😅. FWIW, I prefer that within a distrobox.
- For GameMaker, installing it within a Ubuntu distrobox would probably have been sufficient.
FWIW, I don't think any of these are directly related to "immutability"; i.e. in the case of Bazzite, some subfolders of / being read-only at runtime.
Ah, okay. I was looking at niri's .gitignore 😅. But yeah, I can see it now. Thanks again!
Thank you for the intro, that helped.
Glad to hear it was helpful.
Sounds like Mint not having it is relevant
Yup. FWIW, there's also the security argument; I.e. X11 makes keylogging trivial, while Wayland provides protection against it by default. Having said that, there is experimental support for Wayland in Linux Mint. But, ideally, it needs more time to cook.
Thank you for bringing this up! But, while you've clearly pointed out where to look at, it wasn't quite enough for me to understand what exact content gave it away. Was it
- short/brief .gitignore?
- /target?
- /result?
- Any combination of the above?
I desire to learn this in the hopes of improving my vibe-code radar.
since there’s several issues that have proven unsolvable for me
Could you be explicit? I think it's more beneficial that way. Thanks in advance!
Regarding its architecture, the table says about Wayland the following
Single unified Compositor handles everything
While this has been true in practice, this isn't dictated. For example, very recently, we're finally seeing the decouplement of the compositor from the window manager. Granted, this is still a very recent development and we don't know if others will follow suit. But I'm excited to see where this will lead us.
I suppose it depends mostly on what you intend to do.
FWIW, Wine makes you potentially vulnerable to malware that targets M$ otherwise. As such, I prefer sandboxed solutions. This used to be Bottles for me. However, currently, I don't have any need for it; I play my games through the Heroic flatpak and don't need Wine outside of that.
what is wayland
Basically, whenever an app has a GUI it wants to display, it communicates that to 'the system' with all the necessary details. After which 'the system' does the rendering and whatnot. Wayland is a protocol that defines a set of rules on how this interaction should take place. Hence, technically, it is only (the defining) part of the modern solution.
how important is it?
Very. Basically, either it or its 'predecessor'^[The term is used loosely here, because there's a very big difference between the two.] X11 is involved whenever you want to display/render anything^[Which, to be clear, happens literally all the time. Unless your display needs don't go beyond what was already available on MS-DOS*.] on desktop Linux. As X11 has been abandoned in favor of Wayland, some modern features like HDR or VRR are only found on the latter. On the other hand, I believe Wayland was never meant to offer full feature-parity with X11. Hence, some unsupported edge cases may continue to exist indefinitely. Thankfully, it has come a long way. What remains are some concerns related to accessibility AND the adjustment^[Like, how only very recently Electron got to become proper Wayland-native. Note that Xwayland is included with Wayland as a compatibility layer whenever something is not Wayland-native yet.] of the surrounding ecosystem.
Shortlist of traditional distros, ordered roughly in descending order:
- Linux Mint^[Attracts most noobs and is probs the most popular out of these; no-brainer. Lack of proper Wayland support and not offering (!) a (semi-)rolling release model are the only reasons why the others deserve to be on this list. Otherwise this would sweep clean.]
- Zorin OS^[If you want something slow-moving, but still need/want Wayland.]
- CachyOS^[Arch-based distro, but comes with very sane defaults. Recommended if you're on very new hardware.]
- Fedora^[Relatively bare-bones. Especially compared to all the other distros found on this list. But, if you want a more minimalist approach while preserving excellent defaults, then this is definitely it.]
~~Shortlist of~~ Only^[Technically, any of uBlue's distros qualifies. But Bazzite is a lot more popular than the others. Hence you'll have an easier time finding resources for it.] recommendation for atomic distros:
- Bazzite^[This probs deserves a footnote of its own in which I elaborate, but I got tired. Here, have a flower; 💮.]
As for deciding between a traditional or atomic distro, I'd personally suggest to try out Bazzite first. And refer to their documentation whenever something comes up during initial setup. If at any point, you're not able to get it to work even with the help of its community —^[I know using the em dash here makes me look sus AF, but I can assure the reader that no LLMs were used in the creation of this writing.] be it through their Discord, Discourse or sub~~reddit~~ — then simply pivot to the traditional distros.
view more: next ›
Switching is easy. Sticking to it is harder and involves relearning most of your activities in a new context.
I'd honestly think that CachyOS was more 'sturdy'. Though, I suppose it's curious that you don't mention anything about your troubleshooting attempts. Beyond your rollbacks in hopes of resolving the issue*. If you don't like/want to (learn to) troubleshoot, then reconsider if CachyOS is your home.
FWIW, over (almost) 4 years of Fedora Atomic, I was only once 'forced' to reinstall; which happened in the first week (or so). And that was 100% a user error.
This isn't recognizable to me. Would you be so kind to clarify/elaborate? Perhaps with an example even?
The only time I felt this, was when I just cold-turkey switched to Fedora Silverblue and bashed my head to the wall when trying to implement Madaidan's hardening 😅. But, again, that was just very naive.
NixOS is definitely based. So go for it.
Stateless, and hardened AF. So, probably an amalgamation between your favorite security-focused Linux (be it secureblue or Qubes OS) and NixOS for its impermanence module.