"belltown" wrote:
I'd be curious to know the wisdom as well. It did refer to these features as diagnostic tools in the Developer Blog post that announced their availability: https://blog.roku.com/developer/2016/06/21/roku-os-7-2-dev-highlights/. You wouldn't normally use diagnostic (debugging?) tools in production code, but it doesn't explain why these particular tools shouldn't be used in production.
I got some clarification and that is that their implementations indeed were not intended for production use, while work well while debugging. E.g. say getRoots() might be enumerating thousands of nodes (all nodes) to filter by .getParent() = invalid criteria. That O(n) is fine when troubleshooting but misleading and bad for production. (It may or not be doing that - i haven't looked at the source - but you get the gist)
