No, they haven't done that yet. It's just a proposal, but it's not likely to be formally stopped until 2035.
The reason we've stopped having leap seconds is because the drift between TAI and UT1 slowed down and has actually been very slowly drifting in the other direction.
I don't think we know this do we? we haven't been measuring accurately enough for long enough to be confident that it does in fact cancel out. In fact for the period of time where we've been applying leap seconds they were happening with significant frequency and always in the same direction. It's only been very recently that there's been the realistic suggestion it might drift in the other direction.
If anything people have been suggesting that if we do get rid of leap seconds that we can just wait until the offset is enormous instead (say an hour) because it would take a very long time to happen. But even still, that does actually affect everyday people (because people would surely notice when solar noon is an hour later/earlier). Although pragmatically the obvious solution there is to change timezone instead.
Pre-GPU times you'd be right, but these days a 4U server could have 8 GPUs pulling 350+ watts each. A washing machine sized unit could contain perhaps 4 of these 4U servers so the unit as a whole could be drawing upwards of 11kW.
The magic 50% ownership isn't relevant for that purpose. There are special provisions which means that the Foundation effectively exerts full control over the company because it appoints the entire board.
There isn't a good way to know if a given package is using semver though.
There's a lot of packages in the Python ecosystem that use time based versioning rather than semver (literally `year.minor`) and closed ranges cause untold problems.
I think at this point Apple will just release new versions of laptops whenever new CPU revisions and yields allow. M5 Pro wasn't ready for October so delayed until now.
IIRC Marcan mentioned something he found that had been deliberately put into the Mac boot loader that made booting alternative operating systems easier and perhaps making it possible altogether.
The company I used to work for was developing a self driving car with stereo depth on a wide baseline.
It's not all sunshine and roses to be honest - it was one of the weakest links in the perception system. The video had to run at way higher resolutions than it would otherwise and it was incredibly sensitive to calibration accuracy.
The UK doesn't need to put restrictions in for 3d printing guns because the viable approaches for 3d printing them usually require _some_ off the shelf gun parts not to mention actual ammunition which you can't feasibly acquire in the UK to begin with.
No one forces you to install the pre-commit hook on your local checkout so what you're suggesting is universally the case. You're perfectly free to just run it manually or let it fail in CI or use `--no-verify` when committing to skip the hook if you install it.
It depends on the hooks you're using and how many of them.
For some languages there are some rather slow hooks, and using it on a big monorepo can take a while (a full run across my work's main repo takes minutes). If you update python based hooks all the time then installing and creating the virtualenvs can be slow too which prek speeds up.
The pre-commit tool (which prek is based on) has a large ecosystem of off the shelf checks for various language linters and other checks and a convenient way of writing them (including working out which files have changed and which checks to run based off of that)
The benefit to many of having them as a hook is that you discover it's broken before you pushed your changes, and not when you finally get around to checking the CI on your branch and realising it failed after 30s.
There is of course no reason why you have to have it installed as a precommit hook - many people prefer to run it manually, and the pre-commit tool/prek allows for that.
Maybe if Elon launched himself and the dev team into orbit and didn't use any ground stations and just Starlink terminals he could start getting into legal loopholes.
In the UK we have a convenient way of observing this phenomenon.
The FTSE100 is mostly multinational companies valued in pounds. The FTSE250 is mostly British companies valued in pounds. If the FTSE100 goes up while the FTSE250 stays flat or falls then it means the currency got devalued and there's no real growth.
The reason we've stopped having leap seconds is because the drift between TAI and UT1 slowed down and has actually been very slowly drifting in the other direction.