Suffice to say, like most every programmer out there, if it's based on Algol, i've probably worked with it and can learn the syntax in about 2 hours. Frameworks, of course, come much, much later.
There are folks i work with who eagerly jump from language to language. They herald the joys of Erlang and Haskel, occasionally noting the benefits of Lua.
Me? i tend to be a bit more pragmatic in my age. i have problems that need solutions. i understand that certain languages bring with them certain benefits, and there's an odd level of comfort with some systems that makes them favorites.
The odd thing was that recently i was thinking about writing a program for a task at home, and i kinda sat frozen trying to thing of what to use. This is a bad thing. i code to solve problems, not to just write code. i like to think that i am a bit more practical than theoretical when it comes to solving problems, so while i happily spend time to map out a problem space on paper before i start building, i want to be able to reach into the toolset quickly and get things running.
So, why those?
Well, Go is fraught with issues and catches, but it works reasonably well, and is more than fast enough for most needs. It also straddles the happy middle ground of "interpretive" and "compiled" fairly well that dorking around in code doesn't blow hours of time trying to figure out what the hell just happened. It's also very much built toward being a back end for webservers, which i tend to build a lot of, so there's definitely that.
i'll also say that i'm not advocating that you should do likewise. Each craftsman has his tools, i just prefer having a smaller set. (Heck, my favorite knife is still one that i bought 25 years ago from Wacamaw Pottery for $20.) i'd just encourage you to review your tools and see if you might want to reorder the preferences.