Go programming language – a first impression – 1
I’ve been feeling I should try a new software development language for a while now, to see what life is like outside C++, C#, Java and Javascript. I had a toss up between Clojure, F# and Go. I discounted Clojure because it compiles to Java byte code and I want to stay out of the Oracle ecosystem. I slipped into Go over F# because I could do the Go example without having to get a Visual Studio add on (I know I could do F# from the command line, but I couldn’t be bothered) and the first example worked first time.
I’ve run though the tour and had a play with a few examples. I’m going to reserve judgement on the language itself until I’ve run though Effective Go and fully understood some of the concepts I think are important. In general the language seems very clean and concise (especially compared to Java). The usual problem exists that the main work would be learning all the new libraries and ways of doing things, if I actually had to do something complex, I’d fall back on a language where I knew where to find things (maybe F# would have been better in this regard) because the risk would be much lower.
Something that I think will limit the adoption of Go is the fact that it’s really hard to search for jobs in it (even on Google). I was having a look to see if there is any uptake of it, but trying to search for “go” on JobServe gets you a load of posts requiring “go getters” which is really not what I’m after. If you use “go language” or even “go programming language” then your targeted as a go getting translator! I don’t know if there’s some code in the industry to get round this, like calling it “Google_go”, but until I find the key, even if it’s ace, I’ll never be able to find a job or hire anyone.
Anyway, next time a real bash at the pros and cons.