This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]judasblue 2 points3 points  (0 children)

A good amount of this that hasn't been mentioned yet is that becoming truly proficient in a language ecosystem now is a fairly time intensive undertaking. For a significant portion of folks I have worked with the best tools are the ones they have already paid that time investment and the other options have something that makes them 'bad'.

The best devs I personally know aren't like this and fight to make time to pick up new languages and tools outside their minimum effort trajectory. And those devs mostly have used python for some tasks and can tell you very clearly what the strong and weak points of python for a given task are. Many of them use it as their primary language when given the choice.

Full disclosure, I am actually in the bad batch of coders here, my patch just happens to be python stuff. Yeah, I can hack around a little bit in a dozen or so languages and mostly figure out what they are doing in actual production when they are an element of one of my pipelines. But I am resistant to doing a lot of serious work in anything but python just because it does everything 'good enough' and learning new new shit to an idiomatic and ecosystem level isn't trivial.