It doesn't work for transitive dependencies, so you're reliant on third party composite actions doing their own SHA locking.

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.

You can acquire guns, gun parts, and ammunition quite easily in the UK, and entirely legally.

You need to hold a suitable licence, which isn't expensive and is mostly an exercise in proving to the police that you're not a violent psychopath who's likely to run up to people in cars and shoot them in the face.

But no one forces pre-commit hooks onto you? You can just not install the hook into git and run the tool manually instead.

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.

Ground stations would be the major problem.

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.

At that point, country could just sanction the company, so that it's illegal for its citizens to pay them any money. Seems like a standard thing to do to a company that breaks laws and that you cannot otherwise reach.

Sony have actually been fairly chill about emulators etc. so I'd be surprised if lawyers got involved here.

They actually used an open source Playstation emulator when they released the "Playstation Classic" in 2018.

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.