But the cool thing with laying out your graph like that, is that it has a relational character to it.
You’re essentially dealing in tables and (one/many) to many relationships.
You have a birds eye view of where your entities are allocated and how they are connected.
You still need policies around how you clean them up (remove an entity) and how the edges are affected. But you can reason about that in a similar way as you would in a relational database.
That does not feel like advantage unless you can do relational algebra on it all, though. Without that, it's more like dBase and similar languages of that era, where you had to manually juggle tables and cursors. People did UI that way too, but there was a reason why the OOP approach with object graphs and references quickly became dominant once it appeared - it's still a much more natural way to model this.
But the cool thing with laying out your graph like that, is that it has a relational character to it.
You’re essentially dealing in tables and (one/many) to many relationships.
You have a birds eye view of where your entities are allocated and how they are connected.
You still need policies around how you clean them up (remove an entity) and how the edges are affected. But you can reason about that in a similar way as you would in a relational database.