Croquet as a Superfluid Superplatform

Jon Udel talks about superplatforms and the recently observed blending of the “cathedral” and the “bazaar” as they continue to develop and adapt to the pressures of demand.

The changing cathedral and the evolving bazaar

Superplatform politics

I still think Croquet will be the superplatform of the bazaar.

It blurs or eliminates the boundaries between all these:

"Web services are useful for tying together autonomous systems;
components for coordinating the process distribution within a system;
objects for organizing the code within a process"
Fuzzy Boundaries: Objects, Components, and Web Services

Croquet would make data, code, and UI movement/transmission for sharing/distribution … superfluid.

But that makes security & licensing Croquet’s biggest bugaboo.

Nevertheless, security is a known quantity to solve.

But what about licensing? When data and code stay as objects and not files or streams … and flows from system memory to system memory w/o pausing on the hard drive (other than as raw memory objects in a cache swapfile), how do licensing laws apply?

The streams between systems would contain a flurry of message sends (multimedia content, text, procedures, heartbeats, system/hardware/user status, timing, etc.) all blended together. This would make it difficult to describe what bytes to consider as evidence.