3 ms·
> That is really opposite of the C++ experience, where you have millions of different patterns, techniques, and pitfalls at every corner. Exactly right. And ev
by dilyevsky 5y ago
> That is really opposite of the C++ experience, where you have millions of different patterns, techniques, and pitfalls at every corner.
Exactly right. And everyone who is serious about the mission and not “enjoying the process” is so so tired of c++ with its “millions of different patterns, techniques, and pitfalls at every corner” and c++ devs that need to be convinced not to do crazy shit just bc they can
- TheBlight 5y agoWhen I finished coding C++ professionally the general sentiment of the team was to use less C++ than more. When possible, it was advised to treat it more like C but with classes. The goal was stability above all else and easiness to reason about (for everyone.) That's why when Go was announced its design direction made perfect intuitive sense to me and anyone that spent years writing mission critical C++ on large teams.
- dilyevsky 5y agoYes but many organizations make agreeing on “using less c++” very hard these days. Google kind of managed with their strict review/readability process and pretty much mandatory tooling but it’s damn near impossible in many startups to do the same without a huge political capital to spend. Go takes that challenge from organization level and largely pushes it down to language level.
- TheBlight 5y agoThe loudest voices usually win. I've since exited the tech world but back then the people I surrounded myself with were committed to product and solving business issues in the cleanest way possible and not trying to prove to one another which one of us was smarter.