• randy@lemmy.ca
    link
    fedilink
    arrow-up
    116
    ·
    9 months ago

    If you want a preview of an uncaring and anti-consumer Valve, look no further than the company’s efforts on Mac.

    Valve never updated any of its earlier games to run in 64-bit mode… Apple dropped support for 32-bit applications in 2019

    Funny enough, the only platform with a 64-bit Steam client is Mac.

    I don’t disagree with concerns about monopoly, but the author’s key example is Macs. And from the example, it sounds to me like Apple disregards backwards compatibility (dropping 32-bit support, moving to ARM chips) and Valve isn’t investing to keep up. Meanwhile, Windows has a heavy backwards-compatibility focus, and Linux isn’t too bad either, so no wonder they still get Valve’s attention. So who is being “anti-consumer” in this example, Valve or Apple?

    • DdCno1@beehaw.org
      link
      fedilink
      arrow-up
      66
      ·
      9 months ago

      Agreed. This is a superficial history lesson masquerading as an article. While nothing lasts forever and Steam has its issues, the examples being cited are not supporting the not outrageous prediction that Steam might get worse in the future. It’s just not very insightful.

      Anyone who, unlike the author, actually had to deal with early versions of Steam can attest to the fact that in most ways, the platform has dramatically improved.

    • corbin@infosec.pubOP
      link
      fedilink
      arrow-up
      7
      ·
      9 months ago

      It’s a little bit of column A and a little bit of column B. Apple very obviously doesn’t want the Mac gaming ecosystem to exist in the same capacity as Windows and Linux, but Valve also has an obligation to its customers using Macs to keep the service running well.

      • YaBoyMax@programming.dev
        link
        fedilink
        English
        arrow-up
        35
        ·
        edit-2
        9 months ago

        macOS 10.14 has been EOL for more than 2 years now and basically every Mac released since 2012 is compatible with 10.15. Valve also didn’t actively flip a switch and disable functionality; they’re just no longer providing updates. I don’t think Valve shoulders any blame in this specific case - it’s unreasonable to expect any company to indefinitely support platforms that are effectively obsolete.

        • metaStatic@kbin.social
          link
          fedilink
          arrow-up
          6
          ·
          9 months ago

          I got my first mac a few years back off the side of the road, a 2009 imac that didn’t work. I went to a lot of trouble to find and install the most up to date mac os I could get on it for the challenge and because I’d never used a intel mac before.

          Believe me, they absolutely did just flick a switch. everything about steam worked fine until the day it didn’t even load up. removing support is one thing, actively bricking your product is a total scum fuck move that is just common practice in gaming now.

            • beepnoise@piefed.social
              link
              fedilink
              arrow-up
              2
              ·
              9 months ago

              On Intel Macs, it is fairly trivial.

              On the modern ARM based Macs (the M1/2/3/X processors), it isn’t an option. The only real solution is to use desktop virtualisation software like Parallels to install Windows (ARM based) and try to get Steam going. There are cheaper alternatives to Parallels, but they are often a faff.

        • corbin@infosec.pubOP
          link
          fedilink
          arrow-up
          6
          ·
          9 months ago

          I meant more that the Steam client needs to be fully functional on modern macOS. Dropping older operating systems is more justifiable, but does still add to the picture of Valve not treating Mac owners all that well.

      • verdare [he/him]@beehaw.org
        link
        fedilink
        arrow-up
        12
        ·
        edit-2
        9 months ago

        Yeah, Valve has put a lot of effort into bridging the compatibility gap for Linux. Most of that work could also be ported to macOS, but they just don’t care.

        It’s a shame, because getting 32-bit to 64-bit compatibility working would help Linux as well. I don’t know how much longer distros want to keep supporting 32-bit libraries, and some distros have already dropped them.

        That said, macOS compatibility seems like a non-sequitur for an article calling Steam a “time bomb.” DRM is definitely the bigger issue here.

        • CalcProgrammer1@lemmy.ml
          link
          fedilink
          arrow-up
          11
          ·
          9 months ago

          It’s not just 32 on 64 bit, new Macs use ARM64 processors so x86/x86_64 code is effectively obsolete on Mac. I would love to see Valve pour resources into a cross platform x86 on ARM64 emulation layer though, it would benefit Linux as well.

          • verdare [he/him]@beehaw.org
            link
            fedilink
            arrow-up
            2
            ·
            9 months ago

            The ARM translation may be less of a problem on macOS because of Rosetta. That said, integrating something like Box64 would absolutely benefit both Mac and Linux.

    • teawrecks@sopuli.xyz
      link
      fedilink
      arrow-up
      3
      ·
      9 months ago

      Yeah, totally agree that we shouldn’t go all in on trusting valve, but apple is definitely the anti-consumer one here. I don’t think valve would support DX if they could get away with it. Apple deprecating everything but metal without making it an open spec basically said, “we don’t want anyone gaming on our platform”.

    • Farias@lemmynsfw.com
      link
      fedilink
      English
      arrow-up
      23
      ·
      9 months ago

      To be clear there’s only been a single generation (2006) of x86 based Macs that weren’t 64bit. They’ve been telling everyone since 2007 (well actually earlier even, the final PPC generation was 64bit), that the 32bit was going to go away.

      I hate to defend Apple arbitrarily but all us developers had plenty of notice, and had to specifically reconfigure the default settings on their projects to only be 32bit. If developers ignore deprecation notices for over a decade, then is it really the fault of the other side?

    • GenderNeutralBro@lemmy.sdf.org
      link
      fedilink
      English
      arrow-up
      9
      ·
      9 months ago

      I wouldn’t say Apple disregards backwards compatibility, but they certainly don’t prioritize it to the degree Microsoft does, or that the general open-source community does. For Microsoft, backwards compatibility is their bread and butter. Enterprise customers have all sorts of unsupported legacy shit, and it dictates purchasing decisions and upgrade schedules.

      Apple gave devs and users a ton of lead time before dropping 32-bit support. The last 32-bit Mac hardware was in 2006 (the first gen of Intel Macs); it wasn’t until Catalina’s release in 2019 that 32-bit apps stopped running, and Apple continued releasing security updates for older OSes that could run 32-bit apps for a couple years after that. So that was basically 15 years of notice for devs to release 64-bit apps.

      That was much more time than they gave Classic Mac apps under OS X, or PowerPC apps on Intel. I was much more annoyed when PowerPC support was axed. Only a matter of time until Intel apps stop running on Apple Silicon, too. That’s gonna be the end of the world for Steam games. Ironically, it’s already easier to run legacy Windows and Linux games on Mac than it is to run legacy Mac games.