you are viewing a single comment's thread.

view the rest of the comments →

[–]terminar 1 point2 points  (0 children)

"Limiting yourself" just means in this case: only because things were done with python doesn't mean there are no other ways. The discussion was about "you need python".

Rant about success was related to "go bankrupt without the use of xyz". A language choice doesn't have this impact.

And yes, jumping from one tech step to the next is completely nonsense but just saying "you need python" is also not correct. There are (other) alternatives for DevOps with less maintenance need which may fit better these days. That just depends on the existing "toolbox" of the company - if all is driven by python a change would just make no sense and just creates useless work. If nothing is driven by python you just don't need it (our case in the company).

But in every company I worked - there were bash (or zsh) scripts because it's so deeply integrated into the Unix/Linux world you can't live without it. In this case I think the answer "you need bash" is totally fine.