3 ms·
My one line take on this: You don't use Go for the language design, you use it for the tooling.
by gerbilly 7y ago
My one line take on this:
You don't use Go for the language design, you use it for the tooling.
- Boxxed 7y ago100% agreed -- it's crazy to me how much stuff you can just sweep under the rug when you have fast compilation, a decent debugger, static binaries, and so on. I always tell people, "I love everything about Go except for the language."
- apta 7y ago> have fast compilation, a decent debugger, static binaries, and so on. See Java[1], C#[2]. Both have good compilation speeds (which don't really matter when you have incremental compilation anyway), as well strictly superior debuggers. [1] https://quarkus.io/ https://quarkus.io/ [2] https://docs.microsoft.com/en-us/dotnet/framework/tools/ngen-exe-native-image-generator https://docs.microsoft.com/en-us/dotnet/framework/tools/ngen...
- Boxxed 7y agoOh thanks, haven't heard of those languages.