The main difference is that signing a Windows binary doesn't require any third party review of the app content.

Signing an APK also doesn't require third party review of the app content.

But the context of this discussion is the difficulty of installing an APK from outside the Play Store.

This is the first time I've seen a complaint about giving permission to an app to install another app. The SmartTubeNext issue was due to the developer's keys being stolen. If you want to keep an app signed with stolen keys, you can disable Play Protect. If Play Protect uninstalled apps that Google disliked instead of apps with known vulnerabilities, people would mass disable Play Protect, which would defeat its purpose.

It is still important to declare UTF-8 either in or Content-Type header, otherwise it will usually default to Windows-1252. Yay compatibility!

Even the meta version is picky about where it goes. The whole declaration has to fit inside the first 1024 bytes. Easy to break with a giant comment at the top.

Maybe I'm misunderstanding something about how all this works, but can we have any confidence that 13 million lines of AI-generated Lean code are... correct?

How have we not merely substituted one verification problem for another?

The point of Lean is that it can be mechanically verified by a proof checker.

Not always, there can be bugs in lean. Recently some guy with claimed to disprove Collatz conjecture, only to turn out that there was a bug in lean. I actually have no idea, how anyone can be sure this 13 M lines is meaningful

Lean is adversarial in a way. Lean is better thought of as a constraint language with a verifier that checks if the constraints are respected, than a programming language.

Your job or the LLM's job is to write code that Lean is satisfied with, creating the link between what you're trying to prove, and mathematical axioms.

If you write a bad proof, the Lean constraint checker will tell you, unless there are bugs in Lean itself, or you defined the goal constraint incorrectly.

The discussion of "FLIP (First, Last, Invert, Play)" would be improved by mentioning the View Transitions API, which is basically there to automate this technique.

Original Win95 did not even install a TCP/IP stack by default. It was an optional extra on the CD-ROM.

This changed with OSR2 I believe, when they started bundling IE4.

> Look at any printed media from the last 100 years.

I have, and it contradicts your point. The single space is the nearly universal standard in modern print media.

Even the CBC thinks of London, England before London, Ontario.

Poor London. (Ontario.) (Canada.)

They should have called it New London.

That's in Connecticut and it's older than London, Ontario:

https://en.wikipedia.org/wiki/New_London,_Connecticut

or 'Fake London'

We are fortunate that this individual's stylistic perspective is out there adding spice and variety to the world. I think, however, that most of us would be ill-advised to emulate it.

Orwell's maxim, "never use a long word when a short one will do", is something the best writers have always freely ignored. But it's a reliable guardrail for the writer of merely average skill, steering them toward something passable rather than vomit-inducing.