Oh, I totally agree -- didn't mean to give any impression otherwise. Filling the energy demand gap as quickly as possible with the least impactful generation source should be very high on societal goals, IMO. And it seems like that is what's happening, mostly. Solar, wind, and storage are the largest share of what's being brought up this year:
placatedmayhem
joined 1 year ago
As I understand it, planning new, grid-scale nuclear power plants takes 10-20 years. While this isn't a reason not to start that process now, it does mean something needs to fill the demand gap until the nuke plants (and other clean sources) come online to displace the dirty generation, or demand has to be artificially held down, through usage regulation or techniques like rolling blackouts, all of which I would imagine is pretty unpalatable.
Apple locks old devices out of updates
Dropping support for older platforms happens for a number of reasons, including hardware-level security problems and lack of interest for ongoing maintenance. Linux distributions even drop support for older hardware. Even the Linux kernel itself has dropped support. A decision to not keep supporting a piece of hardware is not the same as preventing updates.
The thing to focus on isn't that Apple halts maintaining its own OSes on older hardware. Rather, we should press hardware makers and regulators on the boot loader locks and other obstacles that prevent end users from installing alternate OSes, especially once hardware makers end OS support for hardware. E.g., older iPads that can't run modern iPadOS but could easily run a lightweight Linux distribution. This applies to more than just Apple, like some Android devices. "Internet of Things" devices are similarly affected -- Belkin halted support for a generation of Wemo smart plugs when a vulnerability came out -- they told consumers to buy new Wemos and provided no alternate path for the older, still functional plugs.
Lots of discussion here of Zed being macOS-only. Multiplatform support is being tracked in this issue for Linux, Windows, and web:
Yes. I'm not sure what you think makes you bad at writing bug reports, but here are tips I give to everyone (my day job involves working with bug reports).
Nominally, a decent bug report should have:
Doing any of these things makes bug reports so much more actionable. You can do it. I believe in you!
Edit: Including a contact method so the software developer can have a conversation with you can also be helpful but not strictly required. Some bug reporting methods do this implicitly, like email bug reports and GitHub issues.