> it started backing up photos until the paltry free tier was reached

How could everyone fill their 15 GiB quota when IIRC by default it only backups the camera roll with lossy compression? Also I've never heard of accounts getting disabled for filling the quota.

FYI I am notoriously bad at taking photos (as is constantly explained to me by family and my partner) and my Phone has 130GiB of Photos and Videos on it as we speak.

Disabled in the sense that you can no longer receive email (which for many is the primary purpose for a Google account), not that you can’t login.

Same thing happened to me and it did not default to lossy. Days later I got the "you will stop receiving email soon" warning in Gmail.

It's 2026, year of decent cameras.

70 seconds long 4K video is 2GB.

Fair enough, I was thinking actual photos. Still, the whole extended family present had that much stockpiled on their phones? Still sounds unbelievable to me IDK.

It's not just the photos that you take going forward, but all the photos you already have stored on the device.

I know, but that's still thousands of photos at original quality, let alone with the default compression, for each member of their extended family present, not just some of them. I barely know a couple people stockpiling more photos than that, let alone an entire family.

No, MZLA is another subsidiary. You're talking about Mozilla Corporation.

> This is a good example of C# light-touch on language design.

Is it? F# code doesn't even need ConfigureAwait(false), one simply uses backgroundTask{} instead of task{} to ignore SynchronizationContext.Current, and this didn't require any language design changes at all (both are computation expressions), but it would for C# precisely because it delegates this choice to the framework.

I guess you can define

  union Union<T1, T2>(T1, T2);

Add a bunch of overloads and you'd replicate for T1|T2 syntax the equivalent mess to (Value)Tuple<...> that eventually became the backing for actual tuple syntax.

> with the optimization that cases with the same type are unified which is still type safe.

To be clear, this requires explicitly using the same field name as well.

That is not what C# has just added to the language though. These union types so far are just wrappers over an `object` field which gets downcasted.

F# offers actual field sharing for value-type (struct) unions by explicitly sharing field names across cases, which is as far as you can push it on the CLR without extra runtime support.

This post is Google attempting outrage bait to push for mass surveillance. The comments can't get much better than the topic.

Debugger positions on the other hand are a pain with these things.

Uh yes, that's what I meant ;)

In C/C++ you have the #line preprocessor directive. It would be nice if Go had something similar.

Go has apparently got //line directives, and this project uses them.

Also Live. Windows Live [whatever], Xbox Live [whatever], Games for Windows - Live, Office Live.

That's still a win for the company if they engage with side media or merchandise, although perhaps not for the gaming industry as a whole. I, for example, don't like LoL the game but I recently watched Arcane, and I've bought more than one artbook from games I don't really feel like playing either.

One great thing about multi-media projects (as in appearing in multiple media separately), is that you can like and engage with just part of them.