It's a solid business model though - get another team to take the risk and develop the app and user base, then when times are tough, buy them out, wring them dry and suck out all the value. In the meantime, don't do any extra feature development on the apps, just run them on maintenance mode with a lean dev team and zero support.
Yes. Buying companies at their actual value and then optimising the and extracting value they can. Considering lot of these startups and how they have acted I don't even consider them anyway evil.
The largest database to ever run on Aurora MySQL runs on PlanetScale, and the largest database to ever run on Aurora limitless also runs on PlanetScale.
We went as far as we could on GCP before PlanetScale. Spanner is amazing but also amazingly expensive. And CloudSQL, also amazing as long as you don’t need write scaling. PlanetScale (Vitess+MySQL plus their branching / deployment and monitoring tools) is just not a combination offered on GCP. And while I didn’t use Aurora, from talking to and exploring AWS it doesn’t really have this combination either.
Instead of managing skills as files, I have been using a simple utility which helps me create, update/attach skills and finally search it across sessions https://github.com/viggy28/recall/
Still a welcome move that they finally added support from Python.
reply