Practically, the VCs should have made some bridge loans to solve the short term problems while we wait to see what comes out of receivership. Some did, and good on them for sticking with it in the hard times.
90 karma · joined November 16, 2022
Practically, the VCs should have made some bridge loans to solve the short term problems while we wait to see what comes out of receivership. Some did, and good on them for sticking with it in the hard times.
These naive smol bean founders don’t struggle to figure out the most tax advantageous way to get paid, let’s not pretend they’re too stupid to read a huge sticker.
And generally speaking the “liberal” cultural values are more popular, so there isn’t really a need for this kind of cultural revanchist strategizing/fund distributing. Which is why you see their projects focused on democratic means rather than the courts.
Could be, but every time I’ve heard academics talk about an industry practice with this level of contempt, they’ve been missing something really obvious. What is it in this case, that syscalls break the purity model in any non trivial real world use case? That performance isn’t actually up to snuff with these runtimes?
Mississippi’s is even more explicit https://avalon.law.yale.edu/19th_century/csa_missec.asp - “Our position is thoroughly identified with slavery — the greatest material interest of the world”
The civil war was fought because slave states wanted to force slavery on other parts of our country, outside their own borders.
Your points are all correct of course, but then that wouldn’t be a preview environment, would it? It would be shared database state in a database staging environment.
Which, for what it’s worth, is also how I have seen this problem managed when it came up.
As for costs, maybe true, but it could also take a lot longer than an hour to bring up a large deployment. And if every engineer is doing this for one hour a week, and you have a few dozen engineers, there’s a 2x cost increase with a tougher capacity planning problem since your load is now tied to your hiring plans.
The obvious problem here is that this approach is far too expensive for any org that isn’t a tiny startup whose production system fits on a half dozen hosts. Consider a column store DB that’s configured in a multi region manner. Is every engineer bringing that up in their preview environment? If they aren’t, it isn’t faithful to a critical production performance constraint. If they are, the company is probably paying twice the cloud costs of their competitors at least, and they don’t get the capacity planning benefits of a fixed staging deployment.