5 ms·
I'm an open-source, solo dev. Not an enterprise dev. I use Go for most of my projects. For me, the biggest hit to productivity are long compile times. One of m
by kjksf 7y ago
I'm an open-source, solo dev. Not an enterprise dev. I use Go for most of my projects.
For me, the biggest hit to productivity are long compile times. One of my projects is ~80k loc C++ app (SumatraPDF) and I pretty much abandoned working on it because the long compilation times are killing me.
Go is good in that regard. My medium sized projects compile pretty much instantly.
I hear Rust is not doing well there.
The second productivity boost is GC (Garbage Collector). I don't want to manually track every allocation (C++) or think about how to contort the code to a form that Rust will be happy about.
Long term productivity is very much why I use Go.
In addition to GC and fast compile times, there's now a very rich ecosystem of libraries for almost everything you might need.
The language has been stable in past 10 years. I don't need to fix the code every major release because language changed (Swift) and I don't need to learn a large number of new things because of significant new addition (Rust).
And for what I use it (backend servers, cmd-line apps) Go is more than fast enough (which can't be said about out languages that have similar productivity, like Python, Ruby, Node).
If there's a C++ competitor I'll be willing to look at, it'll be JAI (when it's released).