4 ms·
Compiling in production? so this is the lang to "go" in case you're such kind of sysadmin which allows a compiler in production. I don't think the article was
by grey-area 13y ago
Compiling in production? so this is the lang to "go" in case you're such kind of sysadmin which allows a compiler in production.
I don't think the article was suggesting that, it's suggesting compiling once before deployment for a given architecture, including all dependencies, as opposed to trying to install dependencies as packages. That is one of the points in Go's favour, as it requires you to produce one binary with static linking, which you can then use anywhere, as opposed to a script which requires dependencies to be installed with it. Of course there are ways round this for scripts (I've packaged entire ruby stacks into apps before for example), and there are downsides (updates to dependencies require a rebuild of the binary).
That's quite separate from how you actually get the binary into production, for which you could use your preferred packaging tools, or a deployment tool like ansible.
Fact 2) The right tool for the job. There is many many sub-jobs to administer a system properly (including security), there is no "one tool".
I don't think he suggested anywhere that Go was the only language that could be used for system administration, just that it would be his preferred language for writing tools from now on. You're reading a bit too much into his statements.
PS Please don't abuse quotemarks like that!
- txutxu 13y agoI see those points where wrong. Others don't. (?) If quotes are a reason to get down-voted, I will be more careful. Sorry.
- grey-area 13y agoI doubt anyone downvoted for minor points of style, more for the aggressive dismissal. I've given you an upvote as don't really feel it deserves the mob-handed moderation, even if it was a bit inciteful. I think this will very much come down to how you see the sysadmin role - in some orgs they play a very close support role and help debug apps etc (polyglot required), in others they might provide more abstract services for developers and never touch app code, only instrument and manage it on the process level (perhaps more where this writer is coming from). So perhaps the wide gamut which sysadmins cover is to blame for your disagreement?
- txutxu 13y agoSure my opinion is affected by my personal experience or career. Anyway, I should have been more careful and respectful in the way to express myself. I don't have anything against Go in particular. And probably my opinion was biased by bad experiences not related directly to Go. Thanks to take the time to explain your view point and make me see.