Releases · CYFARE/HellFire

09 Jan 07:43

CYFARE

v136.0a1

d518e09

HellFire v136.0a1 Latest

Latest

HellFire v136.0a1

GNU/Linux and Windows builds.

Nightly Release Notes

Assets 6

30 Dec 18:14

CYFARE

v135.0a1_FP1

59654cc

HellFire v135.0a1 FP1

GNU/Linux and Windows builds.

Updated: December 30 2024

Starting from this release, AVX2 + SSE4.2 are the default supported instructions. They are supported in most modern CPU's and if you face any issues related to older codecs not being supported, please feel free to build your own HellFire release using the provided mozconfigs.

Reason To Use These Instructions: By using these, your we get huge performance improvements. If this release runs on your system, then congrats! You will see upward of 1.5x to 2x improvement across board. This is due to the fact that the browser will make use of these modern instructions by default, instead of using fallback old instruction sets.

As a side note: HellFire releases based on stable firefox branch may not be possible due to Mozilla upstream not having support for anything above python 3.11x (so in our case, if we use any distro, even if it's ubuntu 24.04 non-rolling release, it's shipped with python 3.12x and ./mach won't run with it). This may not be fixed in future and there are issues opened in BugZilla for this issue. It's funny and really stupid issue where it's clearly stated on Python website that 3.12x is the latest long term supported release with the latest (and very new) release being Python 3.14. While it's not expected to shift to python 3.14x at all due to virtually no toolchain build or migrated towards supporting it, it's very annoying that Mozilla developers have yet to atleast add support for python 3.12x which is being distributed in most stable GNU/Linux distros.. So image someone installing Ubuntu not being able to have their very first build because now the damn python version is lacking from Mozilla side.. Anyway, HellFire may never ship with 'release/stable' versions of Firefox due to these VERY frequently occuring similar brainrot issues originating from Mozilla's side. A previous brainrot issue was when -0fast cflags are completely not working due to their new 'security' architecture, but what if some WANTS to have 0fast builds? Do they now manually switch the flags from your damn source files or makefiles? Wasn't the entire purpose of mozconfig to simplify this manual dumbushitery of playing with makefiles or even the source itself?

Anyway. Enjoy the FASTEST Firefox browser builds in the world!

Nightly Release Notes

Assets 6