I understand there's obvious use cases for Go, but an amazing amount of what we do is taking data from place 'A' (web, socket, file), sending it to place 'B' (another web, socket, file), and then returning a result. Go doesn't buy you much that asyncio won't.
Static typing. Oh Lord is it nice.
When I wrote Python, I never quite knew if there'd be a runtime error (in my code or a library). With Go, there are a lot fewer of those.
All the jobs I see are Ruby + Go or Python + Go, which makes it pointless to learn Go if you don't care about Ruby or Python.
Pretty much, in my career. Sure, i know plenty of languages, but my day job is slinking Go.
I honestly don't want to program in Python any more. I never thought I'd say that, but it's true.
But we will be upgrading a large code-base from 2.7 to 3.x. For things like web data aggregation and parsing, it is hard to beat Python; the tooling in that space is really good.
Definitely looking forward to some unicode pain alleviation from the rewrite.
What date does 1/2-3 mean?
I've had raids cancelled when we agreed on 19:45, but showed up an hour late because he didn't realize that nobody plans raids in GMT.
Är det inte störande när folk börjar prata ett främmande språk mitt i sin post? Å it ens Google Translate hjälp nä dialekt kom i bildn. And as a non-native English speaker, I'd also much rather have the original English version of whatever you're doing, than the half-baked translation that's missing tons of features that are always "coming soon".
No, Unicode-as-default didn't cause this, but the switch shows a switch in culture towards making i18n easy.
You don't see value in meeting customers in their own language and culture?