Exactly! STG, being a "graph reduction machine," inherently makes it easier to understand the relationships between parts of code by representing programs as graphs. Here, I simply reversely translated the generated graph from JavaScript and pushed it into a visual graphical form to make the analysis more intuitively accessible.
I suppose we could have a tool which does such graphical representation automatically for STG, generated from Haskell but I was need to measure its volume in JavaScript form. That's why I was needed to reconstruct it back from JavaScript.
1. https://gitlab.haskell.org/ghc/ghc/-/issues/24744 2. https://gitlab.haskell.org/ghc/ghc/-/issues/23479