• 0 Posts
  • 23 Comments
Joined 11 months ago
cake
Cake day: August 9th, 2023

help-circle





  • Firefox had some major memory leaks when Chrome first launched (2008). It became noticeable with the more tabs you had and the longer the browser was opened. This was also during the days for consumer systems with 16GB max RAM & 32GB on higher end enthusiast systems.

    We also have to remeber that this was 10 years before Google removed their “Don’t be Evil” motto, and there was still a great deal of trust that had been earned by tech professionals.

    So when Chrome came in, had a minimalist UI (for the time) and was light weight and memory light without any obvious memory leaks, it was a performance boost for a toooon of users.

    Chrome has since become a memory hog and is now being developed and pushed by a company that has become heavily enshittified & evil. Firefox has become lightweight, memory efficient, and is an FOSS product that’s not evil and enshittified making it the right choice in 2024, but is going to be an uphill battle that hopefully more tech professionals move to as Manifest V3 becomes a reality.


  • I switched off of Firefox because of those memory leaks. I remeber when it hit the tech news circles when the community contributer that was frustrated with them went in and fixed two of the biggest culprits.

    Then I just didn’t bother til somewhat recently. For the most part, it’s great and does what ilI want/need. Biggest complaint is that some UX overhauls are needed for Mobile FX, especially around tab management.





  • No, what I mean is that salary guarantees you get @ least 40 hours of pay (assuming salaried full-time). If you show up for work and they send you home, as a salaried employee you still get paid. Or if you finish the alloted work for the week early, you still get paid for 40.

    After all of that is when non-exempt comes into play with OT pay according to federal & state regulations and any contract guarantees that go above those regulations.