4 ms·
No doubt those are prominent applications in the Go ecosystem, and thus I can understand why people with little Go experience (or little experience circa 2012-2
by throwaway894345 6y ago
No doubt those are prominent applications in the Go ecosystem, and thus I can understand why people with little Go experience (or little experience circa 2012-2015) have this perception, Go was gaining momentum in the devops and network-services spaces before those apps came to fruition.
Personally, I started using it because it was the only language at the time that made it easy to build and deploy static binaries--I didn't have to learn a DSL to download and wire together a bunch of dependencies (nor run a flaky daemon in the background because the performance of the CLI is so poor) or cargo cult the incantation to package them into an archive or figure out how to make sure that my targets have compatible versions of the target runtime or etc. Similarly I didn't have to figure out how to wire together a third party testing library and integrate it into the build system. Similarly I didn't need to worry about packaging and hosting my libraries or documentation. I also didn't need to operate an external web server like uwsgi or jetty--Go's standard library has a production-quality HTTP server builtin (and its concurrency features made it fast and scalable). The language features were also a pretty big boon: it had value types, first class functions, type inference, "duck typed" interfaces, goroutines, etc and best of all: an ecosystem free from the pitfalls of OOP (inheritance, banana-gorilla-jungle architecture, etc).
Frankly, it's just an amazing little language. I do wish I could take its runtime, tooling, familiar syntax, etc and plug in a different type system, mostly one with rust-like enums and generics; however, the particulars of a static type system are relatively minor factors in the outcome of a given project.
- pjmlp 6y agoStatic binaries were invented when Fortran happened.
- throwaway894345 6y agoCool, but I don’t know what that has to do with anything.
- pjmlp 6y ago> I started using it because it was the only language at the time that made it easy to build and deploy static binaries
- throwaway894345 6y ago"made it easy" != "invented". Anyway, it looks like this thread has devolved into banality, so I'll be ducking out.
- pjmlp 6y agocc -static hello.c -o hello So hard.
- blacktriangle 6y agoAt the time Go was getting started most software was either Java which had to coordinate with the JVM installation or scripting languages which required you to manage a bunch of packages. Static binaries was virtually a feature unique to go from the point of view of popular languages in the domain of web dev and dev ops.