That doesn't have anything to do with the announcement. What the announcement is saying is: previously, if you wanted Gemini to have access to text and chat apps, you also needed to enable Gemini Apps Activity, i.e. the feature that saves all Gemini interactions to the cloud. Now, the settings to enable or disable app access from history tracking are fully separate, so you can have app access enabled (if you want) even if the Apps Activity feature is disabled.

It's a "stream manipulator" function that not only generates a new line, it also flushes the stream.

If you look at the proposal, this is specifically "static reflection", i.e. compile-time reflection. So it doesn't actually have any of the downsides you mention, as far as I can tell.

The reason C becomes relevant to Python users isn't typically because the interpreter is written in C, but because so many important libraries (especially numpy) are implemented in C.

There is nothing special about C.

I wish that were true, but isn't it somewhat wishful thinking? Even an assembly-language Lisp would require an operating system in order to build a functioning compiler, wouldn't it? And operating system APIs are in C.

Edit: more importantly, as the post explains, the special thing about C is the existence of TinyCC.

The whole book is like this, though, and these are specifically supposed to be examples of "good" code. The rewritten time class toward the end, a fully rewritten Java module, is a nightmare by the time Martin finishes with it. And I'm pretty sure it has a bug, though I couldn't be bothered to type the whole thing into an editor to test it myself.

In this context, stabilization refers to the adoption growth curve flattening out.

I'm not totally clear on why signals are used here in the first place. Arguably most C code doesn't "need" to use signals in complex ways, either.

How does the const { None } example type-inference work? The size of the option type can't be known without knowing the type of the Somevariant.

Edit: aha, it doesn't work as-is. It needs to infer the type of elements of foo from usage. https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=05a95c592626b6935ae812527aa6bbc6

I've met people with C++ Stockholm Syndrome, and I think their trajectory is different. There's no asymptotic approach toward zero; their appreciation just grows or stays steady, even decades into their career.

I haven't worked on any teams where all members committed "every 24 hours", and there have always been some branches that live longer than we'd like (usually just unfinished work that got deprioritized but still kept as an eventual "todo"), but most teams I've worked on have indeed followed the basic pattern of only one long-lived branch, reviews and CI required prior to merge, and all feature-branches being short-lived.

What do you mean, "breaking"? This isn't a new encoding scheme, it's an informational page showing ASCII encoding.