656 karma · joined March 12, 2015
[ my public key: https://keybase.io/carlineng; my proof: https://keybase.io/carlineng/sigs/SxKhzboFFXEbC-x-9-NGEtke2DKLBS2wJCzYxL2vPV8 ]
Snowflake is not expensive because of perverse incentives, which is the primary claim of the article. It is expensive because it is a highly differentiated and very sticky product.
As others have mentioned, competition is the ultimate incentive to work on performance. Every dollar of Snowflake revenue is a dollar of revenue that Amazon, Google, Microsoft and Databricks are fighting for.
https://www.cancer.net/research-and-advocacy/clinical-trials...
Shermer's Neck is a condition that impacts a very small percentage of cyclists, and only those who choose to participate in the most extreme of events like Race Across America or Paris-Brest-Paris.
Bitcoin has had 10 drawdowns of 40% or more in its short history of 13 years [0], and yet a mere drop of 33% caused them major problems. Doesn't sound to me like they can blame "a systemic failure of risk management"; more like a profound lack of understanding by these two individuals.
[0]: https://www.livewiremarkets.com/wires/analysing-bitcoin-draw...
Reminds me of the old joke -- an Economist walks past a $100 bill on the sidewalk, but doesn't bother to pick it up. He turns to his friend and declares smugly: "If it were real, someone would have taken it already."
That puts her in good company with pretty much all of the world's most respected economists.
* Facebook doesn't need MySQL to interop with other systems in the same way that blockchain enables.
* Relational semantics are way more complex than what most distributed ledgers technologies offer. A blockchain is more analogous to the MySQL binlog than to MySQL itself. I would guess that Facebook's DB transaction log is orders of magnitude larger than all the blockchains in the world combined.
* Facebook's challenges with MySQL are most likely due to their unprecedented scale. If one were to layer on the governance challenges associated with distributed ledger systems, I would think an upgrade like that would basically be impossible.
> Malloy was designed by a team of people with a lot of experience in understanding the task of extracting meaning from data. Years of constant exposure to SQL resulted in a tremendous sense of wonder at the power of SQL ... and a tremendous source of frustration at how bad SQL is at representing the types of operations needed to get meaningful data out of relational databases, and how difficult it is to maintain and extend a complex set of transformations written in SQL.
> Malloy started as a "clean slate" thought experiment, if we knew all the things we know about data, and about programming with data, and about programming languages in general, and we were designing a query language today, what would it look like.
> In it's earliest form, Malloy looked a lot like SQL, and much of Malloy continues to be influenced by the overall design of the SQL language. It was always the intention that there could be a document that would contain both Malloy and SQL and those would make sense together, perhaps parallel to the way Javascript and Typescript work together.
This statement resonates a lot with me. The VSCode plugin already looks fairly built out, and there's a native BigQuery integration.
[1]: https://looker-open-source.github.io/malloy/documentation/la...
* Confluent Platform (on-prem) accounted for 85% of revenue in 2020, whereas Confluent Cloud (managed SaaS) accounted for 15%. The S-1 makes it clear that Cloud is the future for them. This split makes it a bit tough to interpret their Gross Margin numbers though; as there's no breakout of Cost of Revenue between the two.
* Confluent Platform is subscription-based whereas Confluent Cloud is consumption-based, which further complicates modeling the business.
* Fiscal Year 2017 Cohort must have had some whale customers -- it looks larger than both FY18 and FY19 cohorts (p. 86)
* Expanding net loss -- 97% of revenue in 2020 vs 63% of revenue in 2019. This looks primarily driven by $111.9 million worth of stock-based compensation (tender offer, secondary sales) in the lead-up to the IPO. Excluding that (which is questionable, but still tells us something about how company operations are developing), net loss is ~50% of revenue
* Revenue Growth from 2018 to 2019 was ~130%, but they weren't able to maintain that meteoric trajectory in 2020; revenue growth has slowed to ~58% from 2019 to 2020
[1] https://blog.getdbt.com/future-of-the-modern-data-stack/
I find it interesting that about 2/3 of their trading volume (and thus revenue) is from institutions. Also that 44% of their trading volume is from "Other Crypto Assets", which implies that there must be a rather large bit of institutional activity in "Other Crypto Assets", and it's not just the stereotypical retail crypto investor trading in alt-coins.
[1]: https://www.axios.com/coinbase-valued-100-billion-direct-lis...
"To the extent any registered stockholder chooses to sell shares of our Class A common stock covered by this prospectus, we will not receive any proceeds from any such sales of our Class A common stock."
This is a direct listing, so I think its primarily a liquidity event for investors and employees.