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.
Ruby was better before Rails. When I was deeply into it (I authored one of the stdlibs), neither existed. I left the language partially because of Gems, and Rails didn’t become the killer app (the only reason anyone uses Ruby anymore) after that. I’ve tried to debug someone else’s Rails application a couple years ago, and it was a dependency hellscape. Now, I don’t use Ruby even for the really nice one-liner support that I first loved it for.
You were born too late to experience what Ruby once was sigh.
Yeah, I don’t think I ever got the best intro to ruby… which may attribute to my dislike for it.
When I was in college rails was the big thing at the time and in the software engineering class I had in 2014, they basically gave us preconfigured vms and a quick “here’s how to ruby” before introducing us to rails and the convention over configuration mindset. That was a nightmare experience for me because there were all these magic functions and I had to name my variables certain ways that I didn’t understand the reasoning behind at that point, and it made it much more difficult to differentiate between actual ruby vs. rails’isms.
My only non-rails ruby experience was well after I had graduated and at my first job. Even though that was an experience in and of itself, it was refreshing not having magic classes and just seeing it work like a regular language. I would have preferred that to rails in any world.
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.