Okay -- yeah, that's referring to the fact that the "class" structure is single-inheritance. My current belief is that that works pretty well for Querki: I have yet to come up with a use case where I actually want multiple inheritance.

That's largely because the language is really, in most important respects, duck-typed. That is, you usually care about what Properties a Thing *has*, more than what Model it *is*, and absolutely any Thing can have any Property added to it. So where you would use multiple inheritance in a more conventionally class-based language, you instead just add Properties as needed in Querki.

(The Spaces themselves actually *are* multiple-inheritance: mixins are pretty important for the long-term plans. But that's more cognate to importing multiple packages in a Java-like language.)

Anyway, I have to try it.

Okay, cool. At the very beginning, Alpha is going to be necessarily limited to friends-and-family (for legal reasons), but once I have the company properly incorporated (hopefully pretty soon), I'll be looking for more people to kick the tires, and I'd be happy to have you come try it out then...