Mikrotik is pretty decent but their configuration method drives me up a wall. Ansible helps mitigate the annoyance, at least (in that I only have to figure out/remember the arcane incantation for configuring VLANs once, and then subsequently just have the machine do it).
There are chipset design issues and there are firmware issues. The former is much more difficult to address quickly than the latter, sure.
Torvalds's point, though, is that hardware developers (Intel specifically) keep making changes that "fix" imaginary problems while screwing over compatibility, and trying to shift the onus of making it work to the volunteers who contribute to open source instead of just paying their engineers to produce working firmware.
If the problem were only with defective silicon, I'd agree with you (to an extent), but this is not really an issue with the circuits.
To add to this, spent fuel is over 90% recyclable. If the US were to instate a comprehensive recycling program like France has done, the spent fuel cache could be reduced to negligible amounts.
Signing every message should have zero effect for people who don't use PGP; they'll just have a cryptic block of text at the bottom of the message you sent.
It's overkill to ship your pubkey with every email. Most people just publish to a trusted keyserver and call it a day since pretty much every client worth its salt can look up your pubkey directly.
One way they could increase the housing supply is by severely taxing corporate ownership of single-family homes (and possibly low-occupancy multi-family homes like duplexes).
Give it a grace period, say... 3 months (to cover the cases where a bank forecloses and is sole owner while the house is auctioned), then charge like 95% tax on market value every quarter.
Ted Ts'o was way out of line in that conference and was clearly channeling his inner ca. 2001 Torvalds.
I think Rust is a better path forward for a majority of the kernel/driver code maintained currently, but it is definitely going to take time for it to gain a foothold. I also think there is some condescension on both sides that is completely unjustified and needs to stop.
The hardline C devs that don't want to learn Rust need to accept that at some point they will have to either adapt or pass the torch, and that no amount of whining or bitching in public forums is going to change that.
The Rust devs that are getting upset because people are "attacking" their favorite language need to accept that there will be substantial and impassioned resistance to making broad language changes to a set of projects that have existed for decades. It would be an uphill battle for any language to try to supersede C in the kernel; this is not a condemnation or attack on Rust or its zealots, it's a matter of momentum and greybeard stubbornness.
Well to be fair, you shouldn't have climbed up that toilet in the first place...