Yes, this is true, it won't be noticeable at least
for building GUIs:
the description is only read once before visiting the descriptions
and building the interface. It becomes more of a speed problem when a
query is done over a graph with many described objects.
Ah, I hadn't considered querying.
things, and
frankly, I find myself flushing the cache constantly,
especially during development.
Why that? The cache is automatically flushed when
descriptions change
in your code.
Maybe just a habit I got into, looking over other code, I see use of
MADynamicObject to handle binding of lists that may change and can't be
cached, I think this was the original reason I started flushing the
cache. Also, while in development, sometimes I feel like the cache
didn't flush when I changed a description, however, there's a good
chance that's just a bad perception on my part, like last night when I
was trying to do an instance side description override... felt the cache
wasn't flushing, turned out instead that SettingsComponent had a bug
instead.