There already was such a system with more concrete requirements. It is called the EB5 visa and has a path to green card. What does this new method bring to the table?
Processes can die independently so the state of a concurrent shared memory data structure when a process dies while modifying this under a lock can be difficult to manage. Postgres which uses shared memory data structures can sometimes need to kill all its backend processes because it cannot fully recover from such a state.
In contrast, no one thinks about what happens if a thread dies independently because the failure mode is joint.
Aren't the alternatives you mentioned - icerberg and duckdb - both storage solutions while spark is a way to express distributed compute? I'm a bit out of touch with this space, is there a newer way to express distributed compute?
Resale values are lower in US because they factor in the 7.5k USD tax credit and the state tax credit mostly, there is plenty of demand for used teslas for example.
Intel also had a later chance when Apple tried to get off the Qualcomm percent per handset model. This was far after the original iPhone. Apple also got sued for allegedly sharing proprietary Qualcomm trade secrets with Intel. And Intel still couldn’t pull it off despite all these tailwinds.
Those of us working on smaller codebases may wonder what the big deal is. Facebook had a similar problem leading them to switch out to mercurial.
https://code.facebook.com/posts/218678814984400/scaling-merc...
It is awesome that the problems could be solved in git itself.
Also, kudos to the writer of the blog. It is a really high quality blog post. The percentile measures of performance, survey responses from users etc are very typical of solid incremental approaches to challenges faced by startups except these are internal customers.