3 ms·

Don't know what the 'right' tool is. i think it is easier to code up stuff in Python, as compared to golang. I am much more productive in Python, the language i

Don't know what the 'right' tool is. i think it is easier to code up stuff in Python, as compared to golang. I am much more productive in Python, the language is more expressive, imho. An alternative would be to write in Perl5, perl is pretty much fixed, these days (if you insist on not using containers) Try to compile your go tools in year, or two. If think that you will be hard pressed to find the dependent library versions. Packaging is not the strongest part of go. A version in your package translates to a tag in the referenced git repository, now sometimes people do funny things with their repositories, and older tags disappear. Python and Perl5 are better, at packaging. At least you have all of the older library versions on https://pypi.org/ https://pypi.org/ I think, that the decentralized approach to packaging (as used in golang) is far from optimal. Maybe this is all due to the fact, that google is using a mono repository, internally for their own code. So that they are not eating their own 'dog food'. Sorry for ranting, judgements like 'right tools' really get me going..

travisd 5y ago
“Right tool” is not a value judgement. Python is better suited to certain applications, and go is better suited to others (with overlap obviously). This is partially a function of the language itself (eg, statically compiled or not) and partially a function of ecosystem (eg, writing container tools, go is by far the most pragmatic choice and Python for many ML applications). I think GP was just saying that most times, fewer moving parts is better. Avoiding Docker is great if you don’t need it (especially for a CLI tool). Obviously there are trade offs that must be evaluated in the context of a given problem and domain.
edude03 5y ago
> I am much more productive in Python you may be, but the point is that the time you save writing in python is paid multiple times when each person who wants to use your code struggles to install it and get it working.

travisd 5y ago

“Right tool” is not a value judgement. Python is better suited to certain applications, and go is better suited to others (with overlap obviously). This is partially a function of the language itself (eg, statically compiled or not) and partially a function of ecosystem (eg, writing container tools, go is by far the most pragmatic choice and Python for many ML applications). I think GP was just saying that most times, fewer moving parts is better. Avoiding Docker is great if you don’t need it (especially for a CLI tool). Obviously there are trade offs that must be evaluated in the context of a given problem and domain.

edude03 5y ago

> I am much more productive in Python you may be, but the point is that the time you save writing in python is paid multiple times when each person who wants to use your code struggles to install it and get it working.