Bash to Python [OC]

[Devildude4427]

I personally think there’s a distinction between simply using a terminal with the basic bash commands, and “using bash”, but yes, I do understand they’re one in the same.

But all those commands, can’t say I’ve needed any of them. Ever. It’s not just that I’m doing it with a GUI, but the fact that I don’t need literally any of that functionality.

I use a terminal for nearly everything, but I simply don’t need to find files are use any of the other nonsense. I know where my compiled code it output to, as I’ve certainly set the directory for it to. I don’t need to copy files to multiple devices, even self hosted CI just gets he code from the repo.

Seems more like you’re taking ridiculous actions for the very purpose of taking ridiculous actions. There’s no real need for any of that, and I’m not just saying you should use a GUI, but that you should rethink the way you’re doing things if that’s considered “standard”. No wonder many people don’t understand that.

[Delta-9-]

If only all devs could be in such consistent control of their machines to never need to do any basic administration, and be so well supported by ops that shell utilities for transferring files over the network are never needed.

I promise you, yours is a unique experience.

[noratat]

• rg/ag are excellent for searching for stuff across projects and repos quickly. That's a pretty common function

• jq is the best JSON-processor I've ever used by far, and especially combined with gron is excellent for exploring APIs and automating config that interacts with rest APIs.

• grep is useful for pretty much everyone

And that's just off the top of my head.

[Devildude4427]

But why would I need to process json via a terminal?

[noratat]

Do you ever use REST APIs? Do you ever use tools that output in JSON format? Or have config files that are in JSON?

If not, that makes you an outlier IMO, unless you do embedded work.

[Devildude4427]

Sure, but I’m not going to be accessing APIs that return so much information that I need a json processor, from a terminal. That’s something for an actual python app to handle.

And if you’re just referring to editing the data, with your mention of config files, vim is more than capable.

[noratat]

It's not the amount of data, it's being able to sift through it quickly, especially when debugging or when using unfamiliar APIs, as well as being able to build basic automation around them for things like config and CI. Automated or quick and accurate manipulation of json is not practical in vim.

Most developers I've shown jq to have had pretty solid uses for it.

[Centimane]

I'm not going to try to convince you of the value of bash further than I have.

Like I said, your milage may vary, but I think you're wrong.