UML doesn't scale at all. Its best use is to produce slides. It's less clear than a freeform whiteboard diagram, and actively obstructive to accomplishing a task in practice.
OP's tool has at least the potential to scale to a real codebase in a way that UML could never.
This is often the problem with visual tools. They work well for diagramming small things, but as complexity increases, the visualization becomes very difficult to follow.
The job of diagrammatic representations is not to "scale", but to effectively display and convey the most salient elements of a high-level design. This is just as true of what OP built as about UML itself.
Comments
UML doesn't scale at all. Its best use is to produce slides. It's less clear than a freeform whiteboard diagram, and actively obstructive to accomplishing a task in practice.
OP's tool has at least the potential to scale to a real codebase in a way that UML could never.
This is often the problem with visual tools. They work well for diagramming small things, but as complexity increases, the visualization becomes very difficult to follow.
The job of diagrammatic representations is not to "scale", but to effectively display and convey the most salient elements of a high-level design. This is just as true of what OP built as about UML itself.
No one said the job is to scale. It has to scale with code base complexity otherwise it's useless.