Announcement

Collapse
No announcement yet.

Mozilla Firefox 116 Now Available - Capable Of Wayland-Only Builds

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

  • #11
    i would prefer to use FF flatpak, but i have a problem with fonts on some (few) sites, for example facebook, in these rare sites the fonts really suck, they are fine and grainy...on all other sites they are normal, however this is really annoying.
    For completeness ... firefox flatpak, installed in Tumbleweed - KDE Plasma wayland session.
    Has anyone had the same problem and found a solution?​

    Comment


    • #12
      Originally posted by avis View Post

      That's an option to create a non-portable Firefox build.
      Evil conspiracy!

      It is more likely that distributions start providing different packages for Firefox with and without X.

      And we might finally get Firefox builds for sailfish OS, which doesn't come with X11.

      Comment


      • #13
        Originally posted by avis View Post
        How's that "freedom"?
        And being forced to have Xorg installed even if not used is "freedom"?

        Comment


        • #14
          That should make it easier to discard the X11 code in the coming years so they won't have to put any more development effort into it.

          Comment


          • #15
            Originally posted by avis View Post

            How's limiting freedom become "interesting"? A pure Wayland Firefox build is not any "faster" or "better" than the one which supports X11 as well. Oh, it will save you a hundred of kilobytes of code. At the same time:

            Code:
            $ du -hs /opt/firefox
            224M /opt/firefox
            That's the official Firefox 116 x86-64 Linux build. Yeah, that's really something ... I mean absolutely nothing to talk about.
            It's more secure to drop unused code and close off a door to run something in an insecure old protocol that you forgot to take into account when you wrote some code.

            Comment


            • #16
              Michael

              Typo

              "buidls" should be "builds"

              Comment


              • #17
                Originally posted by avis View Post

                That's an option to create a non-portable Firefox build. How's that "freedom"? What if the user suddenly has an urge to run Xorg? Get wrecked? No Firefox for you? One of the reasons commerical OSes are successful is because they do everything possible to preserve backward compatibility. Linux users on the other hand are obsessed with breaking what used to work in the past. Look where it's got Linux on the desktop so far. Pretty fucking nowhere. Let's celebrate that!

                OMG don't tell this heroic freedom fighter that the Linux kernel is an evil anti-freedom monstrosity because it gives you the option to NOT COMPILE IN S390 SUPPORT!

                IT'S NON-PORTABLE?

                Wanna take your kernel from your laptop and boot it on a mainframe? OH YOU CAN'T! IT'S HORRIBLE.


                Comment


                • #18
                  Originally posted by woddy View Post
                  i would prefer to use FF flatpak, but i have a problem with fonts on some (few) sites, for example facebook, in these rare sites the fonts really suck, they are fine and grainy...on all other sites they are normal, however this is really annoying.
                  For completeness ... firefox flatpak, installed in Tumbleweed - KDE Plasma wayland session.
                  Has anyone had the same problem and found a solution?​
                  For me on OpenSuse Aeon is working fine, maybe is something related to KDE?

                  Comment


                  • #19
                    Originally posted by avis View Post
                    How's limiting freedom become "interesting"?
                    Ah yes, being able to turn off stuff while compiling is "limiting freedom". You are going to have a heart attack when you read the help of any big project's config script, try to compile your kernel or even learn what gentoo use flags are, so many options to disable stuff, so many freedoms limited. Funny as ever, Birdie.

                    Comment


                    • #20
                      Originally posted by avis View Post

                      How's limiting freedom become "interesting"? A pure Wayland Firefox build is not any "faster" or "better" than the one which supports X11 as well. Oh, it will save you a hundred of kilobytes of code. At the same time:

                      Code:
                      $ du -hs /opt/firefox
                      224M /opt/firefox
                      That's the official Firefox 116 x86-64 Linux build. Yeah, that's really something ... I mean absolutely nothing to talk about.
                      The separation itself is nothing to write home about from the perspective on the end-user. It can be useful if you run some public terminal that only supports X or Wayland and you want to reduce the attack surface. It can also be useful if you're a developer looking to track down a bug: does it happen in X-only or in Wayland-only mode? As a developer myself, I can tell you proper separation is always a plus, even if you don't want to translate that to actual packaging.

                      Comment

                      Working...
                      X