2 ms·

This is what happens when you design in a vacuum, ignoring the lessons learned by those who came before you. I know, every language suffers from this to some d

• throwaway894345 6y ago
  You have to compare everything on balance. By not setting out to reinvent Java or C++ or whatever from data 0, Go doesn’t have a lot of features that chafe developers on a daily basis. But yeah, it means it sometimes misses a feature for some use case. But even then those use cases are often marginal, and omitting the feature is often a better design decision. I’m pretty happy with where Go landed—I’m glad it doesn’t look like C++ or Java or C# even if those languages have some cool features. I think on balance Go is an incredibly productive language that performs well on almost all criteria even if it isn’t top of class in any (except simplicity and perhaps developer velocity).
  • Brian_K_White 6y ago
    You already said that.