Go

Developer productivity depends on many factors: environment setup, coding speed, compile times, debugging, testing, deployment, and long-term maintenance. Different languages make different trade-offs across these dimensions. Here’s a comparison based on my experience building production systems: Language Setup Development Debugging Deployment Maintenance Performance C/C++ Complex Slow Challenging Complex Difficult Excellent Java Moderate Moderate Good Moderate Good Good Python Simple Fast Easy Simple Challenging at scale Limited Go Simple Fast Easy Simple Good Good C/C++ C++ offers unmatched control over memory and hardware, which translates to excellent performance when used correctly. However, this comes at a cost: ...

Why should you spend time learning go ? ...

This post is postdated and not really organized. This is about me talking about things that I find amazing but don’t even have the time to get into. If you take a look around, you’ll see that there are lots of languages seeing the light of day each year. I think there are three main reasons for that: It’s not that hard to create a (scripted or compiled) language. Development languages are made to reduce as much as possible the gap between computers and humans. And everyone has a special opinion about this. And a lot of people have special ideas on how we could do that. Languages requirements and possibilities evolve and are backed by previous languages. I’d like to point out few of them. The best language I’ve seen so far is C#. It’s a almost complete rip-off from Java, and most of the other ideas go back to C++ (where the Java guys made some stupid choices). But it also tries to get the ease to get into of languages like VisualBasic. But there are also tons of great news ideas and syntaxes that makes this language very comfortable for a developer to use. ...