Yes, 1M context window since Gemini 1.5 Pro first previewed in February 2024.

Gemini 1.5 Pro actually has 2M!

No other model from a major lab has matched it since afaik.

Edit: err, I see in the comment below mine that Grok has 2M as well. Had no idea!

Google's announcement is also confusingly written, but I believe your interpretation to be mostly correct as best I can tell.

There's a lot of added complexity because of the <1M plan which isn't new, which put the cut at 15% for under 1M of revenue. Also if you participate in whatever these confusing programs are transactions from brand new installs of your app will be only 20% but transactions from existing installs (before the change) will be 25%...

Ugh

That's incredible, so Stripe at 3% plus $0.30 per transactions must be losing money hand over fist!

Because they're moving it to Azure and doing it far too quickly, not taking care to avoid availability issues

It wasn't the migration to Azure that completely borked their PR UI.

Could be.

Or could be that the recent 12 months of 100x increase in code and activity is more than they had planned for when they last did capacity planning.

Vibe-coders, many of them here, often boast about the insane amount of KLoC/hour they can generate and merge.

I've seen this take in another GitHub thread, but are there any stats confirming this? As far as I know a lot of Github stats are publicly available, and can be queried via Clickhouse.

There may be other problems but as someone who's somehow ended up integrating Git into a service twice in my career without even trying that hard to find a reason (it turns out it's weirdly handy in quite a few situations, god I wish it were implemented as a library and not a pile of Perl and shit, and yes I know about libgit2) and has looked into some of Git's and Gitlab's posts about their architectures over the years though the lens of having fought a few of the same beasts, an Azure migration was very obviously going to make things worse.

yeah, ai slop rush

everyone builds off vibes and moves fast! like no, if you are a mature company you don't need to move fast, in fact you need to move slow

the only thing that can kill e.g. github is if they move fast and break things like they do recently

Well that depends on how much traffic that cable was supporting, how much free capacity is available on other cables heading to the same area, how much additional latency the rerouting will add and how sensitive to latency the rerouted traffic is doesn't it?

When was BGP? Or when was NTP?

I think it was a joke based on NTP being a time protocol.

Yeah, then they can start using the auto pen to sign the orders and legislation right?

He simply ignores the courts.

Leopards, faces