'allows' being the operative term here which means that the statement you attempt to contradict has not been contradicted.

How many executives has the UK government sought to prosecute under this law?

> 'allows' being the operative term here which means that the statement you attempt to contradict has not been contradicted.

That's a totally absurd statement in response to "the current government put a new law on the books to give themselves the power to prosecute."

> How many executives has the UK government sought to prosecute under this law?

As stated in my original reply: it came into force in February 2025. It's currently November 2025. It takes time to commit "multiple" offences, particularly given they need to be investigated and convicted. And no, dumping sewage twice doesn't automatically count under any legal regime.

In addition, DEFRA identified that Ofwat (the water regulator) is not fit for purpose in July 2025 and set out a proposal to abolish and replace it.

So yes, it does contradict your statement because the government is literally acting. What would you propose happen instead? That the government hold show trials and just start locking up water company staff and execs?

Misinformation merchants, ironically

It’s not as easy as throwing a sail on top of a boat. Having done a quite a bit of sailing on a yacht, the sail and its supports literally run from the top of the mast to the bottom of the keel.

I suspect for any great deal of efficiency gain you’d need a similar system on cargo ships to support the forces generated.

Actually, you definitely could not plug the entire stream of all tweets from all users in real time into your own application (without huge cost). You only would ever see a subset of tweets via twitters API's and search results, if you wanted the full thing you had to pay for 'the firehose' which was very expensive.

We’ve known that China has been doing this for years to UK universities.. Significant numbers of foreign students are Chinese and universities rely on foreign students for income.

Given the funding and wealth mentioned by other commenters, I think "rely" might not be the right word. More that they are 'accustomed' to getting all this foreign student money. And they like it.

Why would operator overloading be absolutely critical? Just use methods. The pipe operator already has around 15 uses and counting, it doesn’t need more

Because writing a.add(b).divide(c) is miserable

That's a fine approach for "plumbing" type work, you know "join this thing to that thing then call that thing" - and that is most of the code in the world today but it falls apart in math heavy code.

You really just want operators when you're performing tons of operations, it's an absolute wall of text when it's all method calls.

Instead of writing 2+2, you're suggesting writing 2.plus(2) or plus(2,2).

Python gets more bloated weekly in my view.

Removing something, e.g. removing GIL, is usually the opposite of bloat.

Removing the GIL really amounts to adding a bunch of concurrency code all over th cPython codebase. It kind of sucks tbh.

I agree with your latter point on system design. I've had 'big data' interviews where the 'big data' fits in the memory of my desktop machine - so I'm going to give you a very different answer to your over-architected hadoop cluster running over 20 1gb containers or something.

You have to make this a back and forth, not a monologue. Nobody is going to criticize you for tailoring your response to what they want to talk about. Treat it more like a coworker you respect asking you about architecture options, not like a right/wrong graded quiz from college or a chance to assert your knowledge and experience. Your knowledge and experience will show anyway.

I agree but it is not uncommon to find interview processes where a monologue is exactly what they expect and they are unable to have an actual conversation about the topic for whatever reason.

Then it would especially behoove you to spend 2 minutes to figure out which monologue they want.

It's all just prompt stuffing in the end.

Dependency injection in fastapi honestly feels like a horrible afterthought. Flask's g is much easier to reason about, and 99% of projects don't need the 'performance improvements' of async.