3 ms·
> [is Go] currently considered to be in a state where I could start using it today in production Yes. > Would Go language be a good choice now? No. You've b
by 0942v8653 11y ago
> [is Go] currently considered to be in a state where I could start using it today in production
Yes.
> Would Go language be a good choice now?
No.
You've been reading way too much HN if Python isn't modern enough for you. The only way in which Go feels more modern than Python is in its concurrency model (which you are unlikely to need). Unless you are running into roadblocks due to execution speed then you should really just stick with Python. If you take the time to learn a little more Python, it should replace PHP and bash at the very least.
If you're worried about "popularity going forward", you really shouldn't be. Those languages you listed are going nowhere. Python seems to me a surer get for the future than Go.
Really, Go shines when collaboratively building large systems that use concurrency. And it puts things in your way to make sure beginner programmers won't make mistakes, or to make sure everything is clear to read (really, list comprehensions aren't that bad!). It goes out of its way to not be powerful. These are not things you probably want.
Stick with Python. It's great. I use it all the time for scripting and couldn't be happier.
- jaredev 11y agoGreatly appreciate your input here. I've been digging more into Go to get a better feeling for it and I'm arriving at the same conclusion. It's more targeted towards programmers and remote network services, not for systems administration. With Python, I'm able to quickly review the script and modify it as needed then run again right away. The complied nature of Go takes away this advantage. I don't need screaming performance nor low-level access for vast majority of systems admin scripts. Looks more like Python is the better path to stick with.