GNOME Shell 47 Beta Brings Hardware Encoding When Screen Recording & More

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

    GNOME Shell 47 Beta Brings Hardware Encoding When Screen Recording & More

    Phoronix: GNOME Shell 47 Beta Brings Hardware Encoding When Screen Recording & More

    As the next step toward releasing GNOME 47.0 in mid-September, the GNOME 47 beta release is imminent and today the GNOME Shell and Mutter compositor "47.beta" releases were made...

    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
  • You-
    Senior Member
    • Aug 2010
    • 1151

    #2
    Just a headsup that unlike most components, beta is not the feature cut off point for mutter/gnome-shell.

    There wont be much UI change past this point but a lot of feature work in these is under the hood and not a UI change.

    Comment

    • caligula
      Senior Member
      • Jan 2014
      • 3342

      #3
      "- Fixes connecting to WPA2 enterprise networks."

      Isn't this part of network manager? What's the role of gnome here?

      Comment

      • Vermilion
        Senior Member
        • Dec 2021
        • 254

        #4
        Originally posted by caligula View Post
        "- Fixes connecting to WPA2 enterprise networks."

        Isn't this part of network manager? What's the role of gnome here?
        NetworkManager is a backend, GNOME Shell is a frontend, bugs could happen anywhere in between, as is the case here.

        Comment

        • caligula
          Senior Member
          • Jan 2014
          • 3342

          #5
          Originally posted by Vermilion View Post

          NetworkManager is a backend, GNOME Shell is a frontend, bugs could happen anywhere in between, as is the case here.
          So the problem is caused by weak typing in js. Funny how gnome has been switching to js from safe reliable languages. This kind of problems were already solved in 1970s when polymorphic languages with type checking & inference such as ML were invented. That is, 50 years ago.

          Comment

          • mxan
            Senior Member
            • Jun 2022
            • 289

            #6
            Originally posted by caligula View Post

            So the problem is caused by weak typing in js. Funny how gnome has been switching to js from safe reliable languages. This kind of problems were already solved in 1970s when polymorphic languages with type checking & inference such as ML were invented. That is, 50 years ago.
            GNOME has not “been” switching away from reliable languages. JavaScript was picked all the way back in 2008 for purely one reason: a lot of people know it therefore getting new people contributing to GNOME would be easier (back when they actually cared about outside contributions…)

            By now, I think most people have had a chance to look at the text and mockups that Vincent posted of the new desktop shell ideas that came out of the user experience hackfest. Obviously some parts …


            All the underlying components (Mutter etc) are still pure C. And most of GNOME’s core apps are also C, with a bit of Rust making its way in lately.
            Last edited by mxan; 04 August 2024, 07:15 PM.

            Comment

            • krzyzowiec
              Senior Member
              • Jun 2021
              • 245

              #7
              Originally posted by Caligula
              So the problem is caused by weak typing in js. Funny how gnome has been switching to js from safe reliable languages. This kind of problems were already solved in 1970s when polymorphic languages with type checking & inference such as ML were invented. That is, 50 years ago.​
              What is weak typing to you, and how does this example fit that definition?

              Comment

              • emansom
                Senior Member
                • Jun 2015
                • 138

                #8
                Great stuff. Hopefully this brings a more pleasant screen sharing experience in Discord.

                Currently with the software based encoders there's a huge frame latency penalty in games and the resulting screen share has frame skips. Even on Zen 4.

                Comment

                • darkbasic
                  Senior Member
                  • Nov 2009
                  • 3086

                  #9
                  Originally posted by caligula View Post

                  So the problem is caused by weak typing in js. Funny how gnome has been switching to js from safe reliable languages.
                  Why don't they use Typescript? It makes no sense...
                  ## VGA ##
                  AMD: X1950XTX, HD3870, HD5870
                  Intel: GMA45, HD3000 (Core i5 2500K)

                  Comment

                  • curfew
                    Senior Member
                    • Aug 2010
                    • 640

                    #10
                    Originally posted by caligula View Post

                    So the problem is caused by weak typing in js. Funny how gnome has been switching to js from safe reliable languages. This kind of problems were already solved in 1970s when polymorphic languages with type checking & inference such as ML were invented. That is, 50 years ago.
                    No, there's no type system at all in JS. Typing is not the issue anyway, it's that it's completely legal to access non-existent properties on objects.

                    Comment

                    Working...
                    X