3 ms·
Go, by a mile. From day 1 all I wanted to do was write programs that compile down to a single binary, and code that could run on just about any machine I had. T
by 0des 5y ago
Go, by a mile. From day 1 all I wanted to do was write programs that compile down to a single binary, and code that could run on just about any machine I had. That was a far fetched dream for the longest time, and I'd groan about writing things in C++. Now I'm somewhat close to that being a reality and I'm just comfy enough to not look back. It's fast, the stdlib is amazing (in fact I challenged myself to only use stdlib this year and it was pretty awesome), and I don't feel like I'm re-tooling all the time to keep up with the new guys from the last round of hiring, or chasing bugs in abandoned dependencies.
I'd say that the one shortcoming is that making GUI apps is no walk through the park like it was in the VB days, or the tcl/tk days, but it is making significant strides in the form of Fyne, which is a great project with a charismatic team who is working toward making it pretty damn easy to make GUI apps in Go.
One of my latest interests has been using Go's web side to use the browser as my GUI, meaning you can write web apps with it and sweet jesus it's fast.
Just my 2 cents, hope you find your way with the new job.
- deleted 5y ago[deleted]
- mettamage 5y agoI'm currently looking at this question for my own projects ;-) When it comes to a job, I care less about absolute productivity and more about relative productivity, salary, people, culture, location (not in that order). But when it's me, myself and I, then focusing on having a language that I can be amazingly productive in becomes a much bigger priority. I remember Paul Graham once writing an article on how he build a search engine company and was so much faster because he decided to use Lisp instead of C. In terms of productivity, I'd like to see if I can replicate that, at least a bit.