• 0 Posts
  • 11 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.


  • This has me thinking

    The resurgance of sand batteries has been interesting. While not great for converting back into electricity, it’s great for heating and cooling which is a massive portion of our energy consumption. They can also store quite a ton of energy with crazy efficiency, especially when paired with heat pumps. And from what I’ve been able to deduce, they aren’t dependent on beach sand and can use rougher or man-made sand reliably.

    First if we could get enough large buildings and neighborhood/home installation sand battery heating & cooling infrastructure operating with heat pumps. Then when during high times of energy production we can dump the energy into the sand battery infra and help keep the grid stablizied and keeping our heat & cooling overall percentage of use down.

    In the end, we’re going to need tons of solutions and strategies for storing excess production during low demand times. I’m hopeful to see where we go here, the crazy things were seeing in energy storage is extremely interesting. I’m super excited to see the advances were seeing in calcium and sulfur based batteries expand in adoption and the production lines can scale with demand.





  • Feedback:

    Format your README better. And don’t be a condescending jerk and say “wikipedia is your friend”. If you can’t explain what you’re doing here we’re going to question your solution. You don’t have to write a white paper, but enough to show you actually understand the concept enough to explain it in brief then you provide links to detailed refefences.

    Comment your code. Meaningful names are great, but you should be explaining complex concepts and algorithms within your code. This provides clear intent to people using and maintaining your code if implemented directly.



  • As somebody that’s been working on computer hardware since the early-to-mid 90s, installing the drivers before connecting the printer was the norm. It was actually the norm for most peripherals. Just be glad you didn’t have to do manual irq assignment. Hell, that is probabaly the issue, is that the driver installer borked the irq assignment when the device already had a handshake agreement with the hardware.

    I digress though, this shouldn’t have been the pattern for a modern printer in 2007, when PnP had been standard for several years at that point.