• Luci@lemmy.ca
    link
    fedilink
    English
    arrow-up
    44
    ·
    24 hours ago

    32bit does need to go but we’re at a time where a lot of people are switching their main PCs or gaming PCs over to Fedora to get ahead of Windows 10 EoS. The timing in this change couldn’t be worse (even if it’s two versions ahead.)

    It’s bad PR to break Steam and gaming at this time. Valve needs to sort this out on their end but the Fedora Project needs to check in with their users to see what they’re using on Fedora.

    Also loved the gaslighting at the end. Very Linux dev.

    • Possibly linux@lemmy.zip
      link
      fedilink
      English
      arrow-up
      10
      arrow-down
      3
      ·
      19 hours ago

      Steam is kind of junk if you look into how it actually works

      Value needs to get its stuff together

        • Possibly linux@lemmy.zip
          link
          fedilink
          English
          arrow-up
          8
          arrow-down
          1
          ·
          edit-2
          15 hours ago

          It is 32bit and depends on a runtime from a really old version of Ubuntu. It is also proprietary but that is a different issue.

          It would be nice if Value worked with the Fedora project to build something open and modern so that devs could easily package games for Linux. The problem is that Value wants everyone to go though Steam as Steam is where they actually make money. People like to see Value as the good guy but it isn’t all sunshine and rainbows. I can’t really blame them in the end but it is important to realize they have a interest that may not always align with the community.

    • 反いじめ戦隊@ani.social
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      1
      ·
      edit-2
      19 hours ago

      What gaslight?

      Containerizing the 2038 problem won’t fix 32 bit issues that need recompilations.

      Have you set your devices to 2038 and reported the issues your distro needs fixed?

      • Luci@lemmy.ca
        link
        fedilink
        English
        arrow-up
        1
        ·
        16 hours ago

        I’m using multilib for gaming compatibility, I’m not saying we need full _time32 support.

        If I pull 32bit libs for specific applications, why would that affect the kernel or the user spaces apps that are all 64 bit and using 64 bit function calls??

        2038 will break games that make specific calls to 32bit time functions, sure. Thats gonna suck in 12 years from now. But what if instead of breaking compatibility for gaming now, we work towards a solution in the next 12 years?

        • 反いじめ戦隊@ani.social
          link
          fedilink
          English
          arrow-up
          1
          arrow-down
          2
          ·
          edit-2
          6 hours ago

          It’s the other way around: your _time32 libs will fail, especially user apps that call Fedora{Linux _time64. The kernel as of right now is safe for year 2038.

          You have a decade to test everything, report, and fix. Recompilation projects for everything. I want to see year2038_bazzite_safedb.org with all the games and apps you use marked ☑ 2039+ compliant. You need to start now.

          You should have started on 2004. So time to catch up! So yes, let’s database the solutions an app at a time, before the decade is up!