placatedmayhem
Lots of discussion here of Zed being macOS-only. Multiplatform support is being tracked in this issue for Linux, Windows, and web:
Did this ever get better than the initial reviews? It seemed mediocre-to-bad. Steam still calls recent reviews “mixed”.
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.
I agree. Quality is everyone’s job. “QA” as a synonym for “the people that make sure things don’t break” doesn’t actually prioritize quality as an inherent attribute of the product.
Developers need to write tests and build automatic testing harnesses so they can effectively own the code they write and guarantee its quality. A subset of developers might be “QA platform developer” or something similar, but this is to build tooling for testing, not the actual tests themselves.
Designers can’t produce turd of a design and pass the buck. E.g., “That wasn’t the intention of the original design.” and similar terrible defenses. They have to be responsible for the design all the way through to deployment, not just when they call the design spec “complete”. They also need to take feedback from the other groups they work with, instead of thinking their design is above criticism from the non-designer plebs.
Project managers must to prioritize quality initiatives within the project, instead of just driving at feature work or begrudgingly prioritizing critical bug fixes. This includes things like improving developers’ and sysadmins’ lives through tooling and observability. That pile of tech debt the developers and sysadmins has been talking/yelling/screaming about for months/years will eventually fall over and kill everyone, metaphorically of course… unless you work in a safety-critical industry, like medical or transportation.
Sysadmins (and other operator roles, like SRE) have to be empowered to tell everyone else to pound sand when a new proposed deployment is broken or under-tested, or when deployments have been too broken unexpectedly recently.
Yup. FCC abandoning the Fairness Doctrine under Reagan is what brought us sensationalism in broadcast news. Instead, it should have been expanded to cover anything using the term like “news” and “current events”, similar to other protected terminology like “professional engineer”. Cable news never being covered by FD was also ridiculous.
More info: https://www.snopes.com/fact-check/ronald-reagan-fairness-doctrine/
“May you live in interesting times.”