estebank

Could it be that the other differences are driven by differences in the built environment? Like narrower roads making people drive slower, or bollards, or alternatives to driving making it less likely to have people that shouldn't be driving doing so?

Also, 10% is a huge effect.

What would make non-Americans text less?

> But everyone is building them not just American manufacturers

But for, and driven by, the American market.

I would hazard a guess that Silverados sold outside of US, Canada, Mexico and Australia can fit in a single parking lot.

I'm not a doctor and certainly not an oncologist.

The CDC mentions that not smoking and wearing condoms also lower the risk.

https://www.cdc.gov/cervical-cancer/prevention/index.html

Anecdotally people smoke less thant they uses to. Don't know what condom usage rates have done in the past quarter century.

> I assume that this particular shot is not the only thing that has reduced cervical cancer deaths in women under 30.

Why would you assume that when presented with a study that tracks with long standing belief in the medical community that the HPV vaccine works?

https://www.thelancet.com/journals/lancet/article/PIIS0140-6...

The BBC article had that more comparable information: https://www.bbc.com/news/articles/c621z28z138o

> Between 2020 and 2024, no cervical cancer deaths were recorded in women aged 20 to 24 - the first time that had happened over a five-year period.

> Without vaccination, around 23 deaths would have been expected.

Note the first chart in the link showing the historical trend for the 20-24 cohort since 2000 plumetting from 25 to 0.

The third option is to have a variable width length: the top most bit signals whether the next byte corresponds to the length or to the start of the string.

The things I've found:

- RCS doesn't work at all on non-Owner accounts, switching to the owner account is necessary to receive them (I use a secondary account for my "main" account, the owner is left empty except for a Google Fi associated account)

- Immediate auto-update can cause phone to turn off and not turn on overnight (you can change the setting)

- Google Wallet won't work for payments (in Europe you can instead use Curve)

- The default AOSP app selection is in general worse than the Google provided ones (you can install them, after installing Google Play Services, which is sandboxed)

- Getting Google Fi to work required some fiddling initially, pretty sure it was because of my use of the non-Owner account

- Some banking apps will refuse to work (mine work fine)

- You can get Android Auto working, but by default so many things are sandboxed that applications and TTS won't show up unless you spend the time enabling permissions

Overall I am happy with it. It does feel a bit less polished than stock Android (because of the interaction of apps and more strict sandboxing), but for most people who don't care about Google Wallet and are ok installing Play Services and any necessary Google apps, the experience feels pretty much like a de-Gemini'd/de-bloated Android.

Sufficiently advanced stupidity is indistinguishable from malice.

Has actual use increased or is it now just more visible to you?

YIMBYism is about relaxed zoning so that commerce and diverse types of housing aren't physically segregated, but even in the most "free" places industry is segregated because the needs of industry are incompatible with human habitation. No one wants to live next to a refinery, nor should they be put in a position where that's their only option.

(I get that you're being ironic.)

Nitpick: it's Colombia, not Columbia. And the last name is Garcia Marquez. Splitting half of the last name is not generally done. It sounds like calling somebody called McDonald just Mac.

I read books and watch movies to engage and be moved by stories I didn't know I wanted, that surprise me and/or leave me thinking for a while.

I loved Annihilation and it's sequels, not knowing what I was getting into. I would never have come up with those stories. And a one to one translation of the text to screen would have left us without an interesting movie on its own right.

Yes, but no, but also yes.

Editions are for language evolution. Evolving the std does fit the bill. Edition aware path resolution isn't a thing. It will likely be a thing starting with Edition 2027. Range is likely to be the first type to use this feature upcoming.

The full transition won't be completed until 2027 edition, when the meaning of the `..` operator is expected to swap to the new type.

I think you meant TokenStream. They are trees, behind the scenes, because matching delimiters happens early on between lexing and parsing. By the time the rustc_proc_macro::TokenStream is exposed, the rustc_ast::tokenstream::TokenTree is hidden to the proc macro API.

https://doc.rust-lang.org/stable/nightly-rustc/rustc_ast/tok...

https://doc.rust-lang.org/stable/nightly-rustc/rustc_proc_ma...

There's work on edition aware name resolution so that a type with the "nice path" can change over an edition while still accessible through a longer path, but 1) it's not implemented yet, 2) it hasn't been used yet (see 1), 3) if it is ever used it should be done very sparingly (because of the bafflement that can occur if someone follows older docs in the new edition, implementation will come with efforts to mitigate these problems).

Rust macros are Token Trees and provide namespace hygiene, so not quite "text in, text out".

That kind of code doesn't have to hurt performance, as long as monomorphization, inlining or JITting are available to the toolchain. If every single method access is a virtual-table call, then yes, there's an "unnecessary" cost. But you shouldn't be writing high-level looking code in such a language if you care about that level of performance.

VB had case insensitive name resolution.

VisualBasic did that. I think it is a mistake. But that doesn't mean that the compiler can't detect that and tell you how to fix it instead.

If you had a "canonical datastructure database", you could have very short annotations on every standard library for any language that indexes a function to their canonical name. After that you only need to update the database.

In the Rust toolchain we've done the same. It just so happens that rustdoc already has introduced annotations for "aliases" so that when someone searches for push and it doesn't exist, append would show up. Having those annotations already meant that bootstrapping the feature to check the aliases during name resolution errors in rustc was almost trivial. I love it when improving one thing improves another indirectly too.

I really appreciate them going out of their way to do this, being quite aware of the hidden complexity in doing it.

Concepts support (like traits I'm Rust) is necessary for good diagnostics, but not sufficient. It gives you the architecture and metadata that you require to infer what the user wants, but a lot of additional analysis on the decision chain that was followed in order to figure out what is relevant and what isn't.

Even without having concepts, a cpp compiler could conceivably detect at definition time that the template is acting as a generics declaration only, and treat it specially as if it was a "late-bound concept". That would potentially help with codegen, but it would certainly help with making compile errors better. I find it is hard to convince compiler engineers to divorce themselves from what the language semantics are and what the compiler does. As long as the user visible behavior is the same, you can internally handle things differently for conceptually this same feature.

Rust has the same problem as templates with macros. We haven't had a strong need to customize the macrosl evaluation much, but I could very much see us special casing macros that are function like, or have macro arms that can only be a handful of things in order treat them different so diagnostics get better. The only thing that comes to mind thar we do today, is that when a macro call falls through (no macro arm matches), we retry it adding commas in between expressions to see if it was just a typo.

> LLMs are 100% better because they'll give me an answer without trying to sell me their thing or pump me with ads.

Yet.

You can detect with high confidence that a player is aiming at something that shouldn't be visible to them. That goes for both aim bots and wall hacks. The longer they play and the more they do it, the higher the confidence. If you don't want to instaban them because you don't trust the detection enough, use it as a preselection of players to manually review.

Steak doesn't look like a cow either.

There's no reason that kind of client behavior can't be detected server side.

Most of the time is spent figuring what the right thing to do is, not writing the implementation. Sometimes the process of writing the implementation surfaces new considerations about what the right thing is, but still, producing text to feed to a compiler is not the bulk of the work of a software engineer. It is to unearth requirements and turn them into repeatable software.