[kodoque2]

Yeah but I think the point made by this blogpost is to distinguish shallow blub (copy and paste info from stack overflow) from deep blub (go deep into the source code, instrument it and reimplment it) and that the latter allow for generalization and even practical understanding of fringe ideas.

[ThrowawayR2]

I dunno. IMO, there is just too much deep blub around and it loses value too fast for making a significant investment in deep blub to be a practical approach.

[jolux]

There’s a book called CLR via C# that explains the inner workings of the CLR from the standpoint of a C# programmer. I’ve learned more about JIT compilers, static typing, object oriented programming, and language runtimes in general from it than I ever would have expected. I also work in Elixir at my day job, and that book doesn’t describe the BEAM directly, but it gave me a pattern for how to think about how BEAM works that maps better than you might expect.