It seems like that would be a lot of work to maintain. Like as soon as companies start updating stuff (funding rounds, new products etc) your information about them becomes useless.
1. The data entry problem always applies. Unless the data is already entered somewhere in a "canonical" form, it has to be entered again.
2. If the solution is to try to offload the work of data entry to the companies themselves, then google docs and airtable already present a solution since they offer an interface for that.
If you made your money on bay area unicorns, I think its your responsibility to keep reinvesting a portion of it in high growth startups.
If this becomes a trend the bubble will surely burst. For this reason I think we should publicly shame him into keeping the doors on his VC open, or doing something else to contribute to the ecosystem, rather than using all of his money on zero sum political games.
So if you make your money working for some company (say Google), do you owe working for Google something? Do you owe them say, free tutoring classes after you retire for new employees? Free bathroom cleanings after you retire?
Why do you think someone owes someone else money, just because they are rich?
Not sure if this is sarcastic or not. If it isn't, it's ridiculous.
If this is a bubble, it needs to burst (or, preferably but imaginarily, gradually unwind in a non-traumatic fashion) as soon as possible. That's why bubbles are bad - they're going to burst eventually. Better to do it when they're smaller than bigger. And the goal definitely shouldn't be to keep them going as long as possible by artificially sustaining them with more and more speculative money. (Gee, when has that happened before?)
And if it is not a bubble, Chris Sacca no longer investing in high-growth startups is not going to have any impact.
Nobody said the transition would be easy, and nobody said what we have now is the gig economy... The gig economy we were promised is made up of decentralized enterprises built on protocols like ethereum, not market companies.
We are building an orbital communications network and linux based satellite operating system that lets you program your small sat in widely used programming languages, and gives you access to unprecedented, low latency compute and storage on orbit, and enables uninterrupted connectivity to the ground.
what are you doing differently to solve the predictable latency problem? having all the processing happening in the compute cluster so that there isn't enough back and forth to the ground to notice?