> I feel like the representation of the Ruby fib misses the mark though because of how many language implementation details are caught up in it. The article's

> I feel like the representation of the Ruby fib misses the mark though because of how many language implementation details are caught up in it. The article's title is not optimal. It's really about compilation to machine code, and for that you do need all these details. The only "understanding" of these graphs is about understanding what the compiler is doing with the code, it's not for program understanding on a high level.