You're citing a government report to support their position on why we need infinity immigration? Seriously?
The UK population grew from about 58.9 million in 2000 to 69 million in 2025 - an increase of roughly 10 million people. The large majority of that came from immigration.
And you don't think having to house an extra 10 million people is a reason for the housing crisis?
I would suggest you do your own research, and use your own logic and reason rather than blindly accepting government reports into why what they're doing is brilliant.
Maybe you want to byte align some data, or pack to a certain size but keep compat. I think they're going to be rare cases, but I can see it being used.
Fun little game, but I think the questions jump context so much it's a little unrepresentative. It might be better to group things into "packs", which have more real-world representative structure to them.
For example, lots of "editing something.js" file permission requests, and then an "npm publish" is far more normal, and it's more of a risk, if you're used to pressing Y lots and then suddenly out of the blue...
And so the cycle will continue. Always a shame when languages cave like this and add extra unnecessary complexity and error prone hard to parse syntax.
It'll be interesting to see the next language that comes along rejecting bloat in favor of simplicity, and then we can all start again.
One of the things I dislike about B2B is the lack of fine grain control.
With B2C, your revenue grows over time as you grow your userbase. It's pretty predictable, and not too risky.
With B2B, it's more binary. You might go months with 0 revenue, then get some deal and suddenly be profitable. But then there's added risk, as losing a single client can have a massive impact on your bottom line.