3 ms·

A Java tool could be just a file copy too. If we have to support a Go app, and we are a Go team, maybe it's the right tool for the job, even if we have to rein

by txutxu 13y ago

A Java tool could be just a file copy too. If we have to support a Go app, and we are a Go team, maybe it's the right tool for the job, even if we have to reinvent the wheel with configuration management of the systems, backups, auditing, monitoring, provisioning, and "app to really support" integration or control. etc. Else, it has more inconveniences than advantages, imho. Maybe I'm just ignorant on this language (a big possibility) and there is already tools in Go for PXE install some hundred of different servers, to define their O.S. configuration, to have recovery plans, provisioning and backups, to monitor stuff as the packets per second on a switch port, etc, etc, etc. If it covers such typical needs and it's free of surprises and issues... as said... great. Note: I'm not saying python is "the solution" neither. My networks typically need to control more than one scripting/programming language and more than one DSL. And I think that there is no "language" which will free the team of writing custom tools, unless the "sysadmin" level is limited to google-it->copy->paste->makes-ping?->go-to-the-bar (else repeat).

sciurus 13y ago
You're arguing against a strawman. The author didn't say "Throw out all your old tools, sysadmins, and rewrite them in Go"
- txutxu 13y ago
  OK, have to agree on this. But he is saying: ignore the team, ensure your job position increasing the bus factor, ignore security updates best practices. Among other things.
  - lusis 13y ago
    That's not what I'm saying at all. In fact I was pretty clear about that fact. What I said was that I, personally, am going to be writing more personal tooling in Go. I was pretty clear that our team is NOT switching off Python. It's in the last section entitled "This isn't a switching story"
    - txutxu 13y ago
      Sorry, you're totally right. I think I over-reacted and distorted the original article with my personal opinion. Even I'm thinking to dedicate some spare time to explore Go thanks to some articles I've seen in the late days. Next time I will try to be more in line with what is being said. Thanks for reading, understanding and clarifying.
cmccabe 13y ago
You can't install a java tool-- any java tool-- just by a file copy. At minimum, you need to install the proper version of the JVM (different software may need different versions)-- that's at least 50 MB and maybe 100 these days. Then you need a directory with all the jars which the tool depends on-- figure another 50-100 MB or so for that. Finally, you need a shell script to set up the CLASSPATH, set up any JVM arguments you might need (increased heap size, anyone?) and actually locate the binaries. In Go, you just copy the binary to the machine and run it.

by txutxu 13y ago

sciurus 13y ago

You're arguing against a strawman. The author didn't say "Throw out all your old tools, sysadmins, and rewrite them in Go"

txutxu 13y ago
OK, have to agree on this. But he is saying: ignore the team, ensure your job position increasing the bus factor, ignore security updates best practices. Among other things.
- lusis 13y ago
  That's not what I'm saying at all. In fact I was pretty clear about that fact. What I said was that I, personally, am going to be writing more personal tooling in Go. I was pretty clear that our team is NOT switching off Python. It's in the last section entitled "This isn't a switching story"
  - txutxu 13y ago
    Sorry, you're totally right. I think I over-reacted and distorted the original article with my personal opinion. Even I'm thinking to dedicate some spare time to explore Go thanks to some articles I've seen in the late days. Next time I will try to be more in line with what is being said. Thanks for reading, understanding and clarifying.

cmccabe 13y ago

You can't install a java tool-- any java tool-- just by a file copy. At minimum, you need to install the proper version of the JVM (different software may need different versions)-- that's at least 50 MB and maybe 100 these days. Then you need a directory with all the jars which the tool depends on-- figure another 50-100 MB or so for that. Finally, you need a shell script to set up the CLASSPATH, set up any JVM arguments you might need (increased heap size, anyone?) and actually locate the binaries. In Go, you just copy the binary to the machine and run it.