[–] 2 points 48 minutes ago

I can also attest to how slow those animations could make a computer. I think perhaps it’s the difference an integrated GPU makes or perhaps it’s throttling. They are often/usually blocking and it gets irritating.

But - I agree with the premise. Sequoia on an M4 MacBook Pro OOTB with 64GB RAM should be instant for any operation that doesn’t involve a specifically long running operation, but it’s not. Prime example is in the video, changing views of system preferences. It should be as fast as old school HTML hosted locally.

  • source
  • [–] 8 points 3 hours ago* (2 children)

    Every day I’m mad with my parents. They put money into frivolous things like re roofing instead of buying Apple and Microsoft and Amazon at IPO. They only made 200% on the house over 30 years!

    Absolutely unhinged.

  • source
  • Wind (discuss.tchncs.de)
     

    I know this is solarDIY, but it seems like a good place for this anyways. Tl;dr is there a good way to integrate wind and solar without spending a bundle?

    Sun only shines during the day, and as distances from the equator increase, day lengths get shorter, and cloudier, and angles get steeper. However, my location has steady prevailing winds. So much so, there’s a wind farm practically in the back garden.

    Which has me thinking that instead of a ton of panels and a big battery bank (to make use of sunnier days), a little 1kw or so turbine would go a really long way - especially for steady and/or long-running loads like router/server/modem, refrigerator, heat pump…

    I understand that wind turbines make some dreadful power and it tends to be AC. They’re also a bit of a pain to situate but that’s sorta secondary. Let’s say I spin up 10kw of solar, a pile of LiFe batteries, and an eg4 AIO with grid-tie. Is there a reasonable, and safe way to integrate wind? I know one guy who just hooked it straight to his batteries but they were lead acid, and they cooked in a storm. Gave him an excuse to get a big life system instead.

    view more: next ›