Announcement

Collapse
No announcement yet.

Canonical Formulates The 32-Bit Support Strategy For Ubuntu 20.04 LTS

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #11
    Originally posted by Syfer View Post
    Regardless, Valve are moving towards a 64-bit only world, with a recent beta having added a Flatpak style containerization option to run the 32-bit games in... or even all of them, for sandboxing purposes. https://steamcommunity.com/app/22141...5549018366706/
    That's what they should've done originally instead of throwing the toys out of the pram when Ubuntu decided it was time to retire 32bit libs. Flatpak and snap exist in part precisely to solve that problem.

    Comment


    • #12
      Originally posted by RussianNeuroMancer View Post
      Well, I guess as soon as Steam Linux Runtime leave beta this shouldn't be necessary?

      https://www.gamingonlinux.com/articl...ontainer.15384
      I don't use Steam (or anything DRMed) but some of my Win16 apps still require old 32-bit Wine versions because the bugs to restore compatibility broken by "remove the hack. Introduce initial version of proper implementation" are still sitting open.

      Comment


      • #13
        Originally posted by anarki2 View Post
        Steam not having a 64-bit Linux client is ridiculous.
        It's more or less 64bit already, it's a webapp and they don't ship 32bit webkit with it so you can't do much on a true 32bit system.

        Their choice is for games. Especially now with Proton (i.e. running Windows games with Wine) you can't drop 32bit without removing access to a huge list of games

        Comment


        • #14
          Originally posted by ssokolow View Post

          I don't use Steam (or anything DRMed) but some of my Win16 apps still require old 32-bit Wine versions because the bugs to restore compatibility broken by "remove the hack. Introduce initial version of proper implementation" are still sitting open.
          sometimes I wonder if Wine couldn't have been architectured around a different model (i.e. make a decent but somewhat generic core and have additional "plugins" that contain app-specific hacks and function overrides) instead than trying to focus on recreating a true single and always working Windows API (which is a dream even on Windows)

          Comment


          • #15
            Originally posted by jacob View Post
            Ubuntu supports Flatpak perfectly well.
            Every Linux desktop distro supports flatpak perfectly well. The point is that Canonical will never use it by default for a long while still as it is not their own puppy.

            Comment


            • #16
              Originally posted by starshipeleven View Post
              Every Linux desktop distro supports flatpak perfectly well. The point is that Canonical will never use it by default for a long while still as it is not their own puppy.
              Canonical doesn't need to support anything. Canonical doesn't release or maintain Steam. Steam happens to be supported in Flatpak, which means that it's supported on Ubuntu, because Canonical does support flatpak. Therefore the issue of 32bit game compatibility is moot. Lots of people here seem to wish they could blame Canonical for something but there's really nothing wrong with their position.

              Comment


              • #17
                Originally posted by starshipeleven View Post

                sometimes I wonder if Wine couldn't have been architectured around a different model (i.e. make a decent but somewhat generic core and have additional "plugins" that contain app-specific hacks and function overrides) instead than trying to focus on recreating a true single and always working Windows API (which is a dream even on Windows)
                Wine has a Windows Version dropdown that can be set on a per-EXE basis.

                Comment


                • #18
                  Originally posted by Syfer View Post
                  Regardless, Valve are moving towards a 64-bit only world, with a recent beta having added a Flatpak style containerization option to run the 32-bit games in... or even all of them, for sandboxing purposes. https://steamcommunity.com/app/22141...5549018366706/
                  Would sandboxing games via an unchangeable, yet open source steam runtime including proton, be an option to get Anticheat support?

                  Comment


                  • #19
                    Originally posted by ssokolow View Post
                    Wine has a Windows Version dropdown that can be set on a per-EXE basis.
                    not what I mean, that is still a generic API.

                    I mean Wine being designed with a core functionality that expects to be customized and hacked to best support each application in a quick and simpler (and dirty) way than "the proper way" that will never happen as you pointed out.

                    Comment


                    • #20
                      Originally posted by ntropy View Post

                      Would sandboxing games via an unchangeable, yet open source steam runtime including proton, be an option to get Anticheat support?
                      Yes, you only need to sign the runtime and stuff in it with Steam's own private cryptographic key. Then even if it is opensource the anticheat software will be able to determine that it was compiled and signed by Steam and not tampered with by the end user.

                      The anticheat will of course not work in custom builds of the same application(s) and runtime(s) as Steam private crypto key is not available to sign them.
                      Last edited by starshipeleven; 29 November 2019, 04:27 AM.

                      Comment

                      Working...
                      X