You don’t buy from TSMC, but from Intel. Also, AMD also uses TSMC, they didn’t have such problems recently.

Agree, it didn’t do anything to avoid the obstacle. A human could probably see it as an obstacle and try to swerve to the side, albeit not knowing what it is. Not saying it’s possible to avoid, but some reaction would be made.

Well, I’ve been a C/C++ dev for half of my career, I didn’t find Rust syntax ugly. Some things are better than others, but not a major departure from C/C++. ObjC is where ugly is at. And I even think swift is more ugly. In fact, I can’t find too many that are as close to C/C++ as Rust. As for logic… Well, I want to say you’ll get used to it, but for some things, it’s not true. Rust is a struggle. Whether it’s worth it, is your choice. I personally would take it over C++ any day.

Have you tried zed? Written in rust, has many extensions. I gave it a try, I quite like it. It’s blazing fast. But I haven’t tried on an old machine.

Not sure which country you’re from, but I’ve basically lost the any hope I can influence any policy in my country with ANY attitude. I hope I’m wrong about other countries.

Yes, not gonna happen. You know how many new devices get sold simply because old ones are no longer getting updates/software support? It’s planned obsolescence. No modern country would pass a law like that.

So, not the droid we Are looking for… :(

From my small experience with Qualcomm in the past, I’m not too hopeful. In a company I used to work for, we wanted to use one of their SoC with Linux, which they claimed they supported. It was many years ago. But was full of closed binary blobs which even when signing NDAs, we couldn’t get the source for. We’re talking user-space drivers, sensors offloaded to a separate core with closed source firmware etc. It’s Linux, but it’s not Linux in spirit, it feels so closed and proprietary and secretive. They’re coming from Android, which google architecturally enabled vendors to close their drivers by utilizing HAL. It’s the single most significant blow to Linux by any corporation so far. It enabled thousands of vendors to close their shitty driver in user-space and not maintain it for newer kernels (kernel driver is just an IO proxy for user-space drivers). I get that without it, there wouldn’t be Android phones we have today, but I expected them to slowly open up. 10+ years later, almost nothing changed, in fact - things seem worse to me.

How about just having a button on a fob/phone which initiates comms, like in the good old days. You can’t relay the signal if there isn’t one till you press the button. But that isn’t sexy and it’s too similar to traditional cars, so they won’t do it.

Compatibility is iffy on some of the newer ones. Here’s a list of what works for some of them: https://github.com/Dunedan/mbp-2016-linux

Because you can’t end to end encrypt if you don’t have control over both ends. You’d need to trust the other end. Signal doesn’t and their user base especially doesn’t.

It’s often about the money, yes. But highly sought after engineers who can choose where they want to work probably have other criteria too, like not getting stuck in MS corporate ladder long term. That being said, money compensates for a lot of things, that’s just the world we live in.