You can't have any other connections while a Copy-on-Write is happening, not even a logical replication slot. So you keep a read replica that then gets all connections briefly cut for the COW to avoid locking the master instance. Then you re-enable the logical replication slots on both the new, copied instance and the "copyable" read replica to get both back up to date w/ master.
flip-flopping on pricing has led users to feel nickel-and-dimed
i like cursor fine, but check out the forum/subreddit to see people talking like addicts, pissed their fix is getting more expensive
i think this aggressive reaction is more pronounced for non-programmers who are making things for the first time. they tasted a new power and they don't want it taken away.
the founder is on a vesting schedule set with the vc. walking away forfeits his ownership in the company (not sure of the specifics of this weird deal, but this is true in 99% of situations) which returns his ownership to the VCs either directly or functionally.
the only reason he'd walk away is because he thinks other opportunities are higher EV. if he believes this, a) the investors investment is likely worth virtually 0 anyway and b) if it's not, removing a leader who doesn't want to be there probably increases P(success) for the company and further increases the value of the investment.
founder departure isn't good for the narrative, but it's a symptom of an investment going bad, not often a cause.
Good article, but the ChatGPT voice here is strong.
> When you check in, you’re ready to act – without first sifting through a pile of unresolved issues.
> That’s not just a nice feeling – it’s practical. The UI is cleaner. The choices are fewer. The next step is obvious.
> It’s not about urgency. You don’t have to check constantly. Once a day, once a week: what matters is returning to zero with some rhythm.
It's tough for me to assess credibility of authors like this–is this just a DeepResearch report or someone using ChatGPT to clean up an authentic post?
I'm exploring tooling for building these graphs and would love to pick your brain about your use case, if you're willing. No pressure! wade at tractorbeam dot ai
Wouldn't shifting online-first games to access-subscription based pricing make better accounting sense for the publishers too?
Seems like this is less an issue of actual support and more an issue of pricing/access model disconnect.
When a SaaS product ends, it can be frustrating for sure, but it rarely feels like a betrayal in the way ending access to a one-time payment product does.
Or games just shift online-first game pricing to subscriptions. (Fortnite and others have done this already to great success.) The issue here is in a disconnect between pricing model and access model. Mandated uptime seems impractical and unlikely for reasons you listed.
and also git
which makes more sense i guess