At the very least, it results in people filing bug reports and feature requests which may in turn result in their products being more reliable, faster, etc.
I don't know what their policy on accepting code contributions from third parties is, but the prospective value of those contributions should speak for itself.
Yeah I'm familiar with what is in OS X, I have had to use it a few times for work. The fullscreen approach is very clunky. And the window animations are incredibly slow. I'm used to dynamically moving windows around and tiling things quickly. I tried using yabai but it was so slow and buggy there was no point. I think magnet/rectangle helps but it is still a subpar experience.
I tried getting Macs to work for years with yabai etc and came to the same conclusion as you. It's garbage for my workflows. Linux is a million times better.
I decided to get a fully spec'd out Thinkpad X13 AMD 2nd gen instead - 32gb ram, 1TB ssd, 8/16 cores, 16:10 2k screen. All for the whopping price of 1k GBP, a third the price of a similarly spec'd MBP.
I would be less worried about the blade fragments stabbing me than I would be about tumbling into the ground at high speed if a blade breaks. That is a bigger safety concern here. With loss of one corner, you are a tumbling rock.
I'm not sure I would say often. The no speed limit stretches are much more limited than people outside of the country seem to think, and often are temporarily limited when needed, times of higher traffic, road work, near cities or on/off ramps, weather conditions, etc. It is not as much of a free for all as you make it out to be.
We already have laws that make people responsible if they are speeding and crash and hurt someone, and people still do it. The problem with your logic of "there should be no rule unless someone does something to hurt someone" is that people are not always rational, and once someone is hurt or killed it is too late. It is better to try and discourage the behaviour that hurts someone before it happens, rather than after.
Sure, the standard could be made relatively easily, but how do you go about getting every bank to agree on this standard and update their systems to accommodate it, as well as the 10s of millions of POS terminals in the US alone to be updated, as well as all of the major credit card companies, etc.
You get banks to agree by mandating it. Just like the formats of SEPA Credit Transfers are written into law and required by all EU banks to support.
As for rollout: the NFC payment rollout took like a year to get to the point where I haven't encountered any non-NFC terminals since and that required all new hardware. Now that the hardware is out there, adding support for a new system is just a matter of software. At worst, a technician will have to visit every terminal and update the firmware manually (not sure if those things have OTA). "All the major credit card companies" == two, and it wouldn't really matter for their systems anyways since they're not banks, they are now-obsolete middlemen. People could still choose to use cards and vendors would likely still want to support them, there would simply be one more payment option available.
And yes, I agree that this would probably take forever in the US, but they're still using magstripe and the government is too big of a mess to be able to mandate a technical standard or even pass any legislation regarding banking anyways, so I think they have other things to deal with first.
