If they received $36 MM in a fundraise 3 years ago, you better believe that those investors put pressure on the business to grow fast or die trying. Those investors are not looking for a somewhat risky medium % return, they're looking for each company to have a small % chance of being a unicorn.
So who out there is running an investment fund that's looking to make a much more reasonable rate of return off successful but slowly growing companies? Because I would put money into that fund.
Assuming you’re asking in earnest I would begin with S&P 600 Small Cap companies, and see how they got their starts. These are all profitable companies with various levels of earnings growth and indebtedness.
Also commercial real estate fits your criteria almost perfectly.
You probably want the kind of private equity funds that do succession transactions.
Small slow growing businesses tend not to actually need capital very often, so there isn't exactly a huge market for investing in them.
On the other hand, you get a lot of businesses whose owners are getting old / sick of the business. They need somebody to buy them out and install a new management structure.
There are a bunch of funds who do things like that. Look for "Private Equity" as a more broad category rather than just "Venture Capital".
based on what math? I can see how there can potentially be differentiators here and there to raise value, but I can't see how this statement can be taken prima facie
To be honest the main benefit I can see is that the entire DB would be publicly distributed among a large number of independent users which would make the data a lot harder to falsify/hack/corrupt.
However, any system which can achieve the same goal is perfectly valid. This was just my initial thought — probably from my large exposure to blockchains etc
I don't understand this comment. Bigtable requires that each tablet is only assigned to one tablet server at a time, enforced in Chubby. There's no risk of inconsistent reads. Of course this means that there can be downtime when a tablet server goes down, until a replacement tablet server is ready to serve requests.
Right, the contrast I was trying to draw was between what they depict, where multiple nodes are holding a replica of the tablet and performing synchronous replication between themselves, and what BigTable would do, which is to have the entire table copied elsewhere, with mutation log shipping. What they are doing is more analogous to how Spanner would do replication.
Unless you're doing multi-cluster replication, there is no log shipping in BigTable: the data replication within a cluster is taken care of by the underlying filesystems.
I'm not a frontend engineer so I might be misunderstanding, but I thought react was creating representations of dom elements in the render function so that it only needs to apply diffs to the actual dom to keep the browser from eating cpu
Or the slightly longer version of how HubSpot is sort of our CRM system but also a front end for our on-prem Sharepoint and our Microsoft CRM and a couple of other things. It can send some emails, but not all emails, and when it does send emails someone wants them tracked not just by HubSpot but also by SendGrid because that’s how we track mails in parts of the business. Why do we have both HubSpot and Microsoft CRM you ask, well you are, one department really likes one of them and another department really likes the other.
I agree with the sentiment but just wanted to note that this is a legislative bill. often the courts strike down executive action saying that they should get help from Congress, which they're doing here
Arm has a much looser memory model than x86 [1 for a comparison]. It's possible that the random hangs are due to a race condition in PG that doesn't show up in x86 because memory visibility doesn't require as much synchronization.
