• 0 Posts
  • 35 Comments
Joined 2 years ago
cake
Cake day: June 16th, 2023

help-circle
rss


  • Also codecs… even with the right repositories enabled, you’ll tend to install a media application that manages to be utterly incapable of actually processing most media.

    They’ve made strides on this front but it’s still messed up.

    Also sometimes they are too aggressive on one front. Some of the applications you can install from their repository that have some python based features are broken because they can’t handle python 3.13. There’s some ability to install python 3.12 but without much beyond the core making it less useful.



  • I’m not sure exactly what you expect of him?

    It’s not a tantrum, just a statement of limitation. The primary reason for Bazzite to exist is to have a SteamOS-like Fedora. He mentions, in depth, how the ‘simple’ answer about using flatpak doesn’t work, because flatpak imposes isolation in ways that are incompatible with the use case.

    His options seem to be to be “polite” and quiet right up until the change gets approved and implemented and only then yank the rug out from his community, or make the broader community know the implications of removed 32-bit userspace support.

    This seems to be the whole point of soliciting feedback, to know what you are likely to break. It would be supremely odd if you make a proposal, solicit feedback, and call any mention of a bad consequence a ‘tantrum’ when that was the whole point of framing it as a proposal.

    Seems like he needs either Steam to go 64-bit or for Fedora to keep 32-bit since flatpak can’t help and, presumably, he doesn’t want to try to take on the maintenance burden of trying to carry forward Fedora’s 32-bit rpms for the same reason Fedora is trying to get out of carrying them forward. Assuming the broad community decides Fedora 32-bit userspace is still needed, then it’s far less incremental work for Fedora to maintain along 64-bit than it is to independently add it back.







  • Maybe I could see that for Windows server. As more of that market moves to azure, the os matters less.

    I’ve heard rumors that the dom0 equivalent in their azure virtualization platform is now Linux based. They still use an in house hypervisor, but may have moved to Linux as the management stack.

    It’s a long shot, but if Microsoft were moving anything at all, it would be the server product given it actually struggles in market share.

    On the desktop, they just don’t have much reason. They barely evolve the NT kernel so it doesn’t cost them a huge amount. The Linux approach to drivers would completely mess up their driver ecosystem. With the world of modern standby, windows pretty much gave up on long term suspend and instead hibernates, Linux refuses to even try to hibernate with secure boot. The features a Linux kernel brings to the table just do not matter to the windows desktop market. It would be a giant migration expense for no benefit compared to their current strategy of just hosting a Linux kernel as a virtualization guest.

    I mean I would love to use a Linux oriented desktop management instead of Windows shell, but it’s abundantly clear that would be non negotiable for Microsoft, so I’d end up still stuck with my least favorite part of the windows experience even if the kernel were Linux



  • Yep, and then have to opt out all over again the next week when an update decides you need to verify you really mean to opt out again…

    And if you managed to not have an MS account when you installed, interrupt your login and say “you cannot proceed like you have been doing for the past year without adding an MS account now”, and then look up how to get out of that dialog without doing the MS account…




  • The main hiccup for hardware support is GPU support, and as a side effect of the bigger business being in messing with LLMs and that use case preferring Linux, GPUs are getting more Linux attention.

    For example, nVidia drivers went years and years with a status quo of “screw open source, compile our driver and deal with the limitations”. Only after they got big in the datacenter did they finally start working towards being fully open in the kernel space (though firmware and user space still closed source, but that’s a bit more managable)