> worse case interpretations More often than not those end up not having been too far off. The total time to implement might get stretched out, components dir

> worse case interpretations More often than not those end up not having been too far off. The total time to implement might get stretched out, components dirtied by general public resistance will be repackaged or repurposed, and any debate or discussion not in the plan's favour will be actively misdirected. It's a sound strategy, and I hate everything about it. > or only applies to very large platforms Even a single one of which is nigh impossible to avoid. At least some data - either by you, from you, or about you - will end up on AWS/GCP/Azure. A fact of life. > has good parts All of which solve problems that are easily mitigated today, on my own terms, for less effort, and either for free or for cheap. Not a very good deal at all.