I expect it probably wouldn't ever help these situations, but I tried to write the canonical "why adding a flag is a bad solution" answer: neugierig.org/software/blo...

I have tried a few, Kiki's Delivery Service worked the best.

For a slightly older kid (like age 4) I think all of them have themes that can be hard. Even in Totoro, the gentlest one, there is a decent amount of plot around the mom being sick.

I could have recognized it contextually, but the post doesn't give any context that would have suggested it. In a post about authorization I was expecting acronyms from the auth soup, e.g. SAML/IdP/JWT and so on.

Blog post defines DCR on first use, but uses "MCP" without ever defining it.

I think the solution is to provide an opt-out for new strictness checks, e.g. something like --allowImplicitAny. This allows the new TS release upgrade instructions to say "keep --strict, but also temporarily --allowWhatever to keep your build working, then remove that once you get a chance".

I wonder what the impact of this is across TS versions. For example, imagine a new project with --strict on that passes all checks. Next, you want to introduce some new check in the next TS version. If the project tries to upgrade, their build now breaks.

FYI the author of this code assured me he had a better variant of CDC: github.com/buildbarn/go...

FWIW I had this come up too and I called my insurance to ask if it would be a problem. I imagine it's a FAQ, they answered it easily. (For mine it was "once per calendar year", not 365 days.)

lobste.rs requires posts to be tagged, and there's a setting to filter out posts by tag.

I liked this paper's tour through the history of various definitions of what equal can mean:

dl.acm.org/doi/pdf/10.1...

(if you only skim, look for the gray boxes -- the last one on page 12 is curiously relevant to how TS treats class type compatibility)

As others mention, it lets the police harass people who don't "look right". (I had a similar experience in Japan where the police randomly stopped me, asked for my foreign identification card, and searched my belongings. They were polite, but it gave me a new perspective on how bad it could be.)

I keep thinking about how until recently pointers were four bytes, so virtual C++ objects were 4 bytes to copy around. When you combine the Rust layout with 64-bit CPUs our dynamic object pointers are now 16 bytes. It feels like a lot!