3 ms·
I like Go and all but it seems like it is a poor choice for this project. Is there a good rationale for why you would use go to build this?
by spullara 13y ago
I like Go and all but it seems like it is a poor choice for this project. Is there a good rationale for why you would use go to build this?
- pella 13y agohttps://news.ycombinator.com/item?id=5732413 https://news.ycombinator.com/item?id=5732413
- shykes 13y agoWe chose Go, even though we're traditionally a Python shop, for a few reasons: 1) It compiles to a static binary, which makes it very easy to drop docker into an existing ops stack with very little hassle and without having to drag a whole language-specific toolbox along. This has made it easier to adopt docker for devops teams of ruby, python and java persuasion (among others). 2) the language itself is straight-forward, easy to learn and familiar to a lot of people. It's basically a more accessible C. As a result it's been easier to get people from different programming backgrounds to contribute. This is in addition to, you know, the language being good :)
- spullara 13y agoI do like 1) and I agree with your final point. However, all the error handling code, etc is pretty brutal. I imagine someone will put a few scripting languages on top of it at some point.
- crosbymichael 13y agoI have always felt that Go was the perfect choice for docker. Statically compiled binary, fast, simple but powerful.