Awesome discovery!
So, I think there are benefits to having MXML result in a data structure
because it allows run-time manipulation which should turn out to be useful
in testing as well, but if you are welcome to change the data structure for
the JS side if it will result in faster startup.
While
Alex, all,
In 'goog', adding @expose in the JSDoc prevents a property or method
from being renamed in order to keep it available for calls from 'the
outside'.
In FlexJS, the MXMLData solution has (target) property names as strings.
The Closure Compiler won't touch strings and it will not rename
