Also listened in the car but since they've recently shut down the LW tower I can't receive it anymore in the midlands, only occasionally get FM signal.
The original joke for anyone who doesn't know or remember, Michael, the manager, asks his accountant to explain what a surplus is like he would to an 8 year old. Michael doesn't understand this and asks for how he would explain it to a 5 year old, which Oscar does a very good job with explaining and Michael finally understands.
Later the security guard is called upstairs to break a tie on votes for what to spend the surplus on, and Michael starts reciting Oscar's 5 year old explanation, and the guard cuts him off saying he knows what a surplus is.
I have to imagine this is sort of a joke about the audience too as inevitably the writers were considering that audience members might not know what a surplus is, and this kind of joke is an opportunity to explain it.
Interesting though in retrospect they chose good platforms, Mac and UNIX are still around and flourishing and OS/2 died a death, although would a lot of OS/2 stuff have run on Windows?
My young children both love the lawn and I can tell they get a lot from interacting with it, playing on it, etc. It is a little bit of accessible greenery in my small back-garden and I don't need to water it, just mow it occasionally.
With standards it helps to reconcile existing behaviour, rather than create new unproven syntax.
Likewise creating a new syntax for something that already exists means you are just adding to the heap of stuff that needs support on mainstream servers, and as I already said it will probably create compatibility issues as the old deprecated/illegal syntax is removed. This is unnecessary friction.
And really what is the advantage of a new syntax? That needs explaining.
The other issue with adding a separate supported way to do what people did with GET+body is that we will probably see servers slowly drop support for the GET+body approach when QUERY gets widespread support/usage, and then a ton of other stuff will break.
Unless you're really going to improve things or the existing practices are really too painful, standards should follow convention. Even though GET+body is not handled the same everywhere, it's easier to make that the standard than it is to make a new syntax the standard.
Much the same as 'arguments' I can have with LLM's about things where I'm the expert and I know it's wrong, but it will justify its position to the end because it's trained on common misconceptions that exist among less-expert people.
As a consumer who has only tried honest chargebacks within their 'consumer rights' and has never won them, apparently you can fight them, and apparently companies deem them worth fighting.
To add to this YouTube has just added a feature where if you share a link it tells the person who opens the link your profile name, which is doxxing people actively. And further attempt to make YouTube more like other social media.