Pretty bad astroturfing

I think this makes a lot of sense in the context of Zed’s multiplayer editing. Maybe that works well for a small team working on a single product, but that doesn’t seem like it’d scale super well. I loved tight collaboration long ago on online notepads despite constantly breaking stuff for each person…

Is the benefit of using a separate source that you can include images or something else I’m missing? Couldn’t you include context in the commit body?

Thank you for putting this in more generalized terms. I was just thinking replace AI with smart phone and this reads the same.

Unfortunately I think “good faith” goes away quick in the face of “bone shattering”

Smaller more frequent price increases is potentially better than larger less frequent price increases assuming they need the increase to stay profitable? Sounds like they didn’t predict the continued increasing costs.

The company I work for uses GCP and we preciously had intermittent CloudSQL connection errors for a few hours. We reached out and they resolved it after a day or so and said there was a minor incident but I don’t think it was ever publically reported.

Removing access to opus is pretty funny. At least they recognize it’s unacceptable and tell you to go get a refund.

The per-request model was pretty insane.

Hey this is exactly the pattern we have and the bugs we need to catch… yoink?

Yeah that is a “stacked” pr. The tooling is nice especially when have a larger stack and make changes to the first branch. Update refs + push all branches, same with merging and rebasing onto main.