Found myself trying to debug an issue with memory not being garbage collected in a program. It turns out go comes with a tool that shows you the different memory allocations and resource hogs between different goroutines. Super useful so far from what I’ve found on some basic debugging, but still trying to understand how the flamegraph, the visualizations when writing to a png, and some other utilities in there work.
Overall was happy to learn that there was included tooling for that purpose within go itself.
That sounds horrible.
It’s a lovely little language, but gems and rails ruined it. Plus, it’s interpreted, and was evolving a lot at the time, which meant stuff was constantly breaking. That, and the hash table implementation, combined with the obvious inevitability of gems and Rails eventually drove me away.