4 ms·
I love Go and want to see it succeed, but as long as "why I wrote X in Go" is a novel thing, Go maybe hasn't made it yet. There are probably thousands of wonder
by leokun 13y ago
I love Go and want to see it succeed, but as long as "why I wrote X in Go" is a novel thing, Go maybe hasn't made it yet. There are probably thousands of wonderful Python libraries and sure sometimes people decide to talk about why those chose Python, but all of these "Why Go?" posts feel a bit like a forced explanation to the question "Why did you write X in some new language that almost nobody else is using?"
But that isn't true anymore. Lots of people and teams are using Go. You don't need to explain yourself. Just write stuff in Go. Maybe even write about the process of how you wrote your app in Go, but stop making it about the language. It's there, it works. No need to apologize, evangelize or explain yourself.
- yeukhon 13y agoNo, it is totally relevant. Sure you can write docker in Perl in Bash or even in lolcode if you really want to. Each language has its strength and weakness. If everyone is language agnostic why do we bother to invest in Rust when C++ is just good enough in the first place? Why do people here keep inventing a new language? Why Javascript if we could just use Java back in the 90s? Does the language provide some facility that allows docker developers to make docker easier to write and easier to scale than writing docker in Python? Totally relevant. People experiment with new language and hearing Go is scalable and Go is about concurrency - what do these things mean to docker inventors? As a library writer I want to understand what makes Go their choice when Ruby, Python, C and Java seems to the primary languages people use to write system tool. If I were to write a similar tool like docker in Go, what patterns can I learn from reading docker?
- enneff 13y agoI would love to see more articles like this. Not just for Go, but for all kinds of technologies. A lot of real world case studies would make it easier to evaluate new technologies, and help justify decisions to management.
- gress 13y agoIf anything, I'd like to see more 'why I wrote X in Python', and 'why I wrote Y in Java' pieces. I suspect in many cases the answer is 'because I've invested time in learning it' rather than technical benefits. Not that this is a bad reason.