Firefox 115 released - eviltoast
  • darthtyr@fedia.io
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    I have 3 Windows x64 machines:

    • i7 6600u | 16GB RAM | Intel HD 520 | Nvidia 940MX
    • i7 7700HQ | 16GB RAM | Nvidia 1060 (integrated Intel GPU disabled in BIOS)
    • i7 9850H | 32GB RAM | Intel UHD 630 | Nvidia Quadro T2000

    Firefox 115 running flawlessly on all of them. No issues, fast and smooth. Same as previous versions.

  • Sev@feddit.uk
    link
    fedilink
    arrow-up
    0
    ·
    1 year ago

    Been enjoying Edge for a year, but always appreciated FF for it being it’s own thing. Worth a shot?

    • absGeekNZ@lemmy.nz
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      I use edge at work (nothing else available), Firefox everywhere else.

      It would be nice if more add-ons were supported on mobile, desktop is great.

    • Illecors@lemmy.cafe
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      I genuinely think the web has become horrible enough where the browser you use does not really matter from the technical perspective.

      It does, however, incredibly important to have more than 1 engine competing, as currently Firefox is the only mainstream browser not built on chromium/google.

    • glorious_albus@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      1 year ago

      Firefox was great, went to shit for a couple of years, and is now back to being great again. I’ve heard it’s much easier on memory as well.

      It’s one of the few non-chromium browsers left, so you should definitely try it because Google is trying to make their own standards with chromium.

      • deweydecibel@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        It’s literally the only non-chromium browser left other than Safari. That’s why it is critically important that Firefox maintain a presence

    • pascalc@fedia.io
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      I am not seeing any patch submitted to Mozilla by Dashlane on this bug which looks like it is at an investigation phase, is that in a separate bug?