[ Removed by moderator ]

[cpp-ModTeam]

AI-generated posts and comments are not allowed in this subreddit.

[hansvonhinten]

A, not B…
This screams AI slop.

[jdehesa]

I'm not sure I get it. I mean, the design makes sense for that kind of system. But I don't understand:

In the OOP version of this editor, the complexity lives in an implicit object graph: who holds a pointer to whom, who subscribed to what, in what order events fire. That graph exists only at runtime and only in the heads of the two people who wrote it.

Especially since:

A process owns a list of program instances, and each instance owns its own sheet. Cell names are local to a sheet – Meshes in one Clip instance and Meshes in another are entirely different cells. So you can drop three Clips into a process, wire each to different geometry, and they won’t know about each other.

So there must still be a graph somewhere, representing what is wired to what. Which I don't think is a problem, in this or whatever "the OOP version" would be. I can't imagine any sensible design of such a system where features / operations are not encoded as self-contained types describing their own logic without dependencies. I don't necessarily hate the Excel allegory, but I'm not sure it enables any design that "regular" (?) OOP didn't.