Yeah. See, when you wanna hit scales like that, then allocations matter, because a garbage collector comes into play, taking up time, allocations take up timeR30; So when you wanna hit scale like that, or PrometheusR30; I think they were just talking about half a million requests a second. When you wanna try and hit scale like that, allocations become really crucial. But I don’t think it’s something for people to get caught up in really early on, especially if you’re new to the language, because sitting there trying to trace down your allocations just kind of hinders the fun of developing it and being productive in this language, and seeing how fast it runs on its own without you having to give much thought to it. I think that if you’re starting out you should not be concerned with that. Save that for later. I think that it’d just become too daunting, and it’d be harder to fall for the language, because at that point you might as well be trying to learn C, right?
Speaking of taking on things new, two questions I wanted to ask: one is hiring – for you, Travis, how has that been? We haven’t really had to do too much hiring for Go people, so I don’t know how big the pool is. Do you guys struggle to find talent? Do you train talent?