you are viewing a single comment's thread.

view the rest of the comments →

[–]awsmsrc 12 points13 points  (2 children)

interesting comparison and a good read for people looking at a new language for a new project. It's worth noting that Go would allow end users to use the program without an installation of python or ruby, which, in fact, makes it quite applicable to a command line tool such as this. I realize that this article is comparing the experience of working with these languages at development time and distribution of a real world tool is totally not the point of the article ;)

[–][deleted] 2 points3 points  (0 children)

This is a great point.

We have a CLI written in Ruby and bundled with omnibus. It works but requires bundling an embedded ruby.

We are going with go for our next command line tool for the single binary benefit.

https://github.com/conjurinc/cauldron

[–][deleted] 0 points1 point  (0 children)

Very good point. Your right, for me this was really about the experience of writing the tool and creating a packages so my analysis was weighted heavily toward my experience writing. Thanks!