I guess that’s why I enjoyed working with Go so much.
100% serious, because my next job uses Go - Why? Everything is painful and takes way more code than it should.
Its compiler is very fast, the libraries are great, importing new packages is easy and straightforward, HTTP libraries and frameworks are some of the best I’ve worked with.
Compared to Java or C#, there really isn’t that much boilerplate.
Why is “the compiler is very fast” a good argument though? I’d rather the compiler spends 1 minute and does it well and optimized instead of 10 seconds and I have to write Go, honestly.
In many cases, for many things, compiling isn’t the part that takes the longest in development anyway.
There are some great aspects to Go, like how you can map fields of a struct to json properties for Marshal/Unmarshalling and channels is an interesting idea, but other than that it doesn’t seem to me like there’s a lot of pros over, say, C# which is almost ubiquitous in many industries these days.
C: What if you used emojis for pointer (
*) and deref (&) signs?God, I haven’t worked with Tcl for a while. Really don’t miss it.
Isn’t that what Rust is?
no.
go is more like simpler C, zig (will be (hopefully)) more like better C
makeis inevitable, because everything is a dependency.There is no wisdom, no truth, only endless dependencies. /s
SQL?
