Announcement

Collapse
No announcement yet.

SDL3 Begins Dumping A Lot Of Old Code: GLES1, OS/2, DirectFB, WinRT, NaCl & More

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

  • SDL3 Begins Dumping A Lot Of Old Code: GLES1, OS/2, DirectFB, WinRT, NaCl & More

    Phoronix: SDL3 Begins Dumping A Lot Of Old Code: GLES1, OS/2, DirectFB, WinRT, NaCl & More

    It was just a little more than 24 hours ago that SDL 2.26 released for this widely-used library by cross-platform games and other software for abstracting software/hardware interfaces. With SDL 2.26 released, SDL 3.0 is now in development. One of the first stages of that big Simple DirectMedia Layer update is removing a lot of old platform code and other obsolete targets...

    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

  • #2
    sdl 3.0 is also expected to make some modernization changes like being the release to prefer wayland over the x.org server by default, hopefully pipewire by default
    rip sdl 3.0

    Comment


    • #3
      Originally posted by Monsterovich View Post

      rip sdl 3.0
      In a computer running wayland compositor, i think defaulting to direct communication to wayland is better than going through xwayland. A computer won't be running wayland and native x.org server at the same time anyway.

      Comment


      • #4
        Originally posted by Monsterovich View Post
        rip sdl 3.0
        It's not forcing users to have Wayland or pipewire. Your comment makes no sense.

        Comment


        • #5
          Should have removed pulseaudio and x11.

          Comment


          • #6
            Originally posted by RejectModernity View Post
            Should have removed pulseaudio and x11.
            They can not do this. The software that is build on top of SDL might still have X11 dependencies and will need to go the xwayland way because of that. This can also be true in 10 years from now on. So X11 is still very important to have in SDL. Qt and GTK need to do the first step by deprecating X11 support, so it's known that it will be removed withing the next major version.

            For pulseaudio, I'm with you. I dont see pulseaudio to be around in 2 years anymore.

            Comment


            • #7
              Originally posted by billyswong View Post

              In a computer running wayland compositor, i think defaulting to direct communication to wayland is better than going through xwayland. A computer won't be running wayland and native x.org server at the same time anyway.
              That is of course the goal but there has been a lot of bugs and issues in the SDL Wayland backend to work out to get it on par with X11. This has required changes in other places also, like the creation of libdecor and some Wayland protocol additions (afaik), and so on.

              Comment


              • #8
                If they really want to remove jack support they should remove pulseaudio support first: pipewire is in a better shape to replace pulseaudio than jack yet.
                ## VGA ##
                AMD: X1950XTX, HD3870, HD5870
                Intel: GMA45, HD3000 (Core i5 2500K)

                Comment


                • #9
                  Originally posted by darkbasic View Post
                  If they really want to remove jack support they should remove pulseaudio support first: pipewire is in a better shape to replace pulseaudio than jack yet.
                  However, PipeWire hasn't even had it's 1.0 release yet, and even the developers themselves suggest using pipewire-pulse or other audio solutions built on top of PipeWire for now.

                  So, not a good idea to remove support for Jack and Pulse.

                  Comment


                  • #10
                    Originally posted by OroWith2Os View Post

                    However, PipeWire hasn't even had it's 1.0 release yet, and even the developers themselves suggest using pipewire-pulse or other audio solutions built on top of PipeWire for now.

                    So, not a good idea to remove support for Jack and Pulse.
                    1.0 doesn't matter; it's just a version number. Remember how long it took Wine to reach 1.0, despite being in good shape?

                    Comment

                    Working...
                    X