Fedora 42 Eyes Replacing SDL2 With sdl2-compat To Leverage SDL3

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • phoronix
    Administrator
    • Jan 2007
    • 67061

    Fedora 42 Eyes Replacing SDL2 With sdl2-compat To Leverage SDL3

    Phoronix: Fedora 42 Eyes Replacing SDL2 With sdl2-compat To Leverage SDL3

    The SDL2 library is widely used by cross-platform games and other software. Fedora 42 is eyeing the possibility of replacing SDL2 with the sdl2-compat code so that by way of this compatibility layer the newer SDL3 version will ultimately be used instead...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite
  • cend
    Phoronix Member
    • Dec 2023
    • 112

    #2
    When SDL5 releases we may have to witness a terribly performing dependency chain...

    Eventually statically linking all further compatibility layers into sdl12-compat and turning on link-time optimization would become the preferrable option to extract performance on old games.

    Comment

    • Jumbotron
      Senior Member
      • Jul 2015
      • 1192

      #3
      Whatโ€™s the story with Ubuntu ? I donโ€™t recall seeing their stance recently on this matter.

      Comment

      • King InuYasha
        Senior Member
        • Jul 2007
        • 156

        #4
        Originally posted by cend View Post
        When SDL5 releases we may have to witness a terribly performing dependency chain...

        Eventually statically linking all further compatibility layers into sdl12-compat and turning on link-time optimization would become the preferrable option to extract performance on old games.
        It doesn't work that way. The compatibility libraries use dlopen() to avoid symbol conflicts.

        Comment

        • user1
          Senior Member
          • Sep 2019
          • 1108

          #5
          Honestly, this is a really dumb idea. It's another story if we talk about SDL 1.2, which saw its last release many years ago, but SDL 2? While it may not receive new features anymore, its development still hasn't ended and it receives bug fixes. If you look at their milestone page on Github, you'll see that they still plan to release SDL 2.32 and maybe even 2.34. I don't understand how the user will currently benefit from the switch to sdl2-compat. The latest versions of SDL2 work perfectly, even with SDL_VIDEODRIVER=wayland. If anything, the switch to sdl2-compat will probably lead to a more buggy experience, first because it was in development for just 2 years and second, because SDL3 hasn't even had its first official stable release yet. Just look at sdl1.2-compat. It has been in development for much longer, and it still doesn't run all SDL 1.2 games flawlessly like native SDL 1.2.

          This is yet another example why I left Fedora (even though my initial impressions of it were good). They sometimes seem to push new tech even when it's clearly not ready. Another examples are systemd-resolved, which for still unknown reason randomly stops resolving DNS, and tuneD which seems to be more buggy than power-profiles-daemon and uses more CPU since it's entirely written in Python unlike PPD.

          I mean don't get me wrong, I still think Fedora is a very good distro, but I just disagree with some of their decision making.
          Last edited by user1; 06 December 2024, 10:22 AM.

          Comment

          • StarterX4
            Senior Member
            • Aug 2015
            • 305

            #6
            2040 be like: Old games running through sdl12-compat through sdl2-compat through sdl3-compat through ... ... though at least they use SDL6 ๐Ÿ˜…

            Comment

            • skeevy420
              Senior Member
              • May 2017
              • 8514

              #7
              Originally posted by user1 View Post
              Honestly, this is a really dumb idea. It's another story if we talk about SDL 1.2, which saw its last release many years ago, but SDL 2? While it may not receive new features anymore, its development still hasn't ended and it receives bug fixes. If you look at their milestone page on Github, you'll see that they still plan to release SDL 2.32 and maybe even 2.34. I don't understand how the user will currently benefit from the switch to sdl2-compat. The latest versions of SDL2 currently work perfectly, even with SDL_VIDEODRIVER=wayland. If anything, the switch to sdl2-compat will probably lead to more bugs, first because it was in development for just 2 years and second, because SDL3 hasn't even had its first official stable release.

              This is yet another example why I left Fedora (even though my initial impressions of it were good). They sometimes seem to push new tech even when it's clearly not ready. Another examples are systemd-resolved, which for still unknown reason randomly stops resolving DNS, and tuneD which seems to be more buggy than power-profiles-daemon and uses more CPU since it's entirely written in Python unlike PPD.

              I mean don't get me wrong, I still think Fedora is a very good distro, but I just disagree with some of its decision making.
              From what I can tell, they've been keeping sdl2-compat relatively up to date with SDL2. It looks like their endgame is to "pull a Vulkan" or "pull a Wayland" with SDL using SDL3 and sdl*-compat...Move everything to SDL3+compat and be able to drop legacy cruft.

              Yeah, Fedora is a rolling test platform. Pushing things forward and seeing what breaks is what Fedora does. It can suck when you're the kind of person that updates for the sake of updating. That's also why Fedora supports their versions for an extra six months (IIRC) and why you shouldn't necessarily upgrade from A to B right away or ever. Perhaps just skip right over to C when it comes out.

              Comment

              • caligula
                Senior Member
                • Jan 2014
                • 3308

                #8
                Originally posted by StarterX4 View Post
                2040 be like: Old games running through sdl12-compat through sdl2-compat through sdl3-compat through ... ... though at least they use SDL6 ๐Ÿ˜…
                I remember when I started doing game programming with allegro in the 1990s. Soon after switched to SDL 1.2, then SDL 1.3 in 2005 or so. SDL 1.3 is basically SDL 2.0. it's surprising there are still games using this 20+ year old code. Small games. Nobody cares about their code base anymore.

                Comment

                • F.Ultra
                  Senior Member
                  • Feb 2010
                  • 2024

                  #9
                  Originally posted by StarterX4 View Post
                  2040 be like: Old games running through sdl12-compat through sdl2-compat through sdl3-compat through ... ... though at least they use SDL6 ๐Ÿ˜…
                  yep but then again you will be able to play your extremely old games by then on the latest hardware and software stack and not only will everything work but those old games can also utilize some of the new benefits. Beats having to create something like Wine but for old Linux versions.

                  Comment

                  • ahrs
                    Senior Member
                    • Apr 2021
                    • 549

                    #10
                    Originally posted by user1 View Post
                    This is yet another example why I left Fedora (even though my initial impressions of it were good). They sometimes seem to push new tech even when it's clearly not ready. Another examples are systemd-resolved, which for still unknown reason randomly stops resolving DNS, and tuneD which seems to be more buggy than power-profiles-daemon and uses more CPU since it's entirely written in Python unlike PPD.

                    I mean don't get me wrong, I still think Fedora is a very good distro, but I just disagree with some of their decision making.
                    To play devils advocate, I would say that these bleeding edge changes are good because it results in more exposure to the software they're using which in turn uncovers bugs and ideally results in them getting fixed and the software improved as a result. Don't get me wrong, I'm still going to keep using Unbound as a stub resolver over systemd-resolved but I think the job Fedora does in moving software forward is invaluable. If they didn't do it, who would?

                    Comment

                    Working...
                    X