You are only browsing one thread in the discussion! All comments are available on the post page.

Return

venia_sil ,
@venia_sil@fedia.io avatar

Firefox ESR is basically the LTS of Firefox. Over a portion of the normal ("stable") Firefox's release cycle, ESR will get security fixes and backports, but nothing that changes interface or expected UX behaviours. It's basically there for keeping an environment that is consistent and predictable over a reasonably long term (~1 y) which is why it's the Firefox version that gets shipped with eg.: Debian.

In general, ESR is the default version I install for anything clients-wise that for some reason requires that we don't intervene client machines too much (including maintenance). It's fire-and-forget once you have the usual extensions rolling like uBlock Origin.

Memory wise it's also quite reasonable in its usage and I've found it's far more responsive to customization of in-RAM memory usage patterns than stable, nightly or develiper Firefox, who tend to ignore or misinterpret my requests such as "only use up to 16 MB of cache in RAM".

One part where maybe ESR is too conservative is the HTML / CSS lexer. Because it's intended to stay stable over very long periods it gets stuck with stuff like still not accepting CSS :has(), and it seems the next ESR won't support it either, whereas Nightly does already. Also, because behaviours are retained as long as possible, bug UI breaking changes such as the migration off Australis or the incorporation of the Extensions Button are a more jarring clash in ESR than in normal Firefox, because you get all those workflow-changing changes in one BIG update.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • [email protected]
  • All magazines