I read this overview several times and I remain confused. It seems like a rehash of plan 9/network-is-computer paradigms. I get all the reasons that is interes

I read this overview several times and I remain confused. It seems like a rehash of plan 9/network-is-computer paradigms. I get all the reasons that is interesting now- networking is REALLY fast and lots of cache hierarchy and other assumptions in kernels just don't apply any more- but to place the emphasis on the areas of innovation on the use of tables and transactions as core distributed primitives for applications...is strange. While maybe beneficial for system programmers, it definitely isn't a more understandable paradigm for application programmers- very few of whom who write code that saves data understand the varieties of transaction semantics. And in terms of applications, what decades of failed "database under the filesystem with typed object storage" work has shown also that the data types and semantics applications need are always more imaginative than those exposed at lower levels. Someone used to working with graphs, when given tables, is going to walk away. Where is the ML layer that optimizes under a "save this thing" surface that actually presents a new stable abstraction? But in true armchair architecture sniper fashion, I'm going to leave my confusion as is and move on. Best wishes to them.