How did we reach this point?
Firefox was somehow a bigger resource hog than Chrome before I dumped them. Probably worse at doing the whole "your browser is your computer" thing.
>>107655680>>107655693HOLY HECK GUYS THE BROWSER IS USING THE RAM I BOUGHT TO BE USEDNO FRICKEN HECKEN WAY
>>107655718>NO MY BROWSER MUST CONSOOM THE RAM>MY RAM MUST BE CONSOOMEDyou are the kind of retards who justify using react in start menu
>>107655680WHY ARE YOU RUNNING A 32BIT BINARY?
>>107655759If you use a good OS it will drop the RAM usage on everything when you open a process that requires actual ram usage eg a video game (even something as shit as w11 knows how to do this)Don't buy RAM if you don't want to see it in use homie, we are in 2025, software is not THAT shit, it just knows how to utilize shit now
web is cancer.pic related is exactly like any web developer thinks.>>107655693Firefox is pivoting to be a AI first browser experience. It going to be way worse when they slowly roll new "features" for the 2% of the 10000 users that still use firefox in 2025.
>>107655680>>107655784
>>107655786>great workbased sir doing the needful
>>107655766Name 10 reasons why he shouldn't
>>107655784Even before you get to that half of OP's RAM is still just sitting on the table. Given Windows uses 20-30% RAM at idle on an unmodified setup Firefox isn't hogging anything. The average person being autistic about RAM probably has to manufacture a scenario where RAM usage will actually matter, like running an intensive game and then opening as many websites as possible until the whole system shits itself and even in a manufactured scenario the CPU might be the bottleneck. Whenever this topic comes up 1% of the time it's someone saying>I was compiling something and my system shit itself And 99% of the time it's>I opened task manager and the number is big why isn't the number small it's orange that means bad
>>107655796/thread
>>107656535kek
>>1076562351. The 4 GB Memory Ceiling32-bit binaries can only address 2^{32} bytes of memory. 2. Fewer CPU Registers64-bit mode provides 16 general-purpose registers, doubling the 8 available in 32-bit. 3. Weak Security Randomization (ASLR)Address Space Layout Randomization (ASLR) relies on a large address space to hide where code is stored.4. Limited Hardware ProtectionsModern security features like the No-Execute (NX) bit are native and mandatory in 64-bit environments.5. Slower Floating-Point Math64-bit binaries use SSE2 for mathematical operations. 32-bit binaries often default to the legacy x87 FPU, which is significantly slower for media encoding, encryption, and scientific calculations.6. Native 64-bit Integer HandlingProcessing large numbers (greater than 2.1 billion) takes a single CPU cycle on 64-bit systems. A 32-bit binary must use multiple, slower instructions to achieve the same result.7. Software Translation OverheadRunning 32-bit software on a 64-bit OS requires a translation layer (such as WoW64 or multilib). This adds a layer of complexity and a slight performance penalty that native 64-bit apps avoid.8. Ecosystem DeprecationMainstream operating systems like macOS and many Linux distributions have moved toward "64-bit only." Keeping 32-bit support requires legacy libraries that bloat the system and increase the attack surface.9. Lack of Compiler OptimizationModern development tools are optimized for x86_64. 10. Hardware InefficiencyModern processors are physically designed to be most efficient when executing 64-bit instructions.
>>107656535compiling man
>>107656597not really.https://www.ghacks.net/2016/01/03/32-bit-vs-64-bit-browsers-which-version-has-the-edge/their performance is usually nearly identical, but with less RAM usage for 32-bit programs. i can only speak for windows program, don't care about linux the server os.
>>107656597t. clanker
