From the day I first read about Croquet, I’ve been trying to wrap my head around the secure, persistent object model. Building applications — or even understanding what applications can be built — depends on this model, which is still under development by the Croquet architects. Four months later, I’m still pretty lost.
I’m most interested in how the pieces fit together, and the abilities afforded by that configuration. Alas, I’m not clever enough to understand and express this entirely in the abstract. The more specific I get in components and abilities, the more specific I need to be as to a plausible way of implementing it. Otherwise, I get lost. I hope (unrealistically?) that no one takes this as a proposal. In fact, I’d be perfectly happy if the same abilities were achieved for Croquet with different implementations. I’d even be ok with a different set of abilities, as long as I understood what and why they were. But I gotta start somewhere. This is public because I would like help in improving my understanding, and also because my blog is from me personally. It does not represent anything from U.Wisconsin or the Croquet architects. Maybe by putting even wrong stuff into print, we can clear up misconceptions.