I completely *detest* that the MongoDB *shell* is just a fucking jS interpreter with extra API calls sprinkled on top and whoever came up with that idea should have all their commits reverted immediately, working with that thing is a punishment!

I don't even know a way to parse and chew through the json it spits out in my own json viewers, as it's "Extended", and none of my editors understand that!

Ugh, haven't been this frustrated with a tool for a while...

Just use pymongo ffs.

@magicMirror That lands me in literally the same mess as with jS, I don't have an issue with the language itself (I could so-so understand it...), my issue is that the administration shell environment should not be programming language based at all!

All administration activities are made that much more complex when I have to parse machine-made texts instead of getting output in nice human-readable form.

If the administration commands like db.getCurrentOps() would yield something more human readable, or had aliases like showProcesses, then I wouldn't have an issue, but it's like having to write "SELECT * FROM information_schema.processlist" then getting an output not in a nice table, but in a bloody SQL Dump file that a machine can read just fine, but that's frickin' impossible to easily make heads or tails of as a human.

I took a look at this pymongo thing, and it is, again, a wrapper to work with MongoDB from Python, and not a fully flashed out shell replacement...

@Aldar hehe, mongo is that type of mess that happens when you make dramatic changes to a project's scope. Just imagine if the newest Intel GPUs had to have analog PWM outputs for motors.
In mongo's case, it was originally built to perform MapReduce jobs written in JS, just as it was made to be a general purpose database.
So, yeah, the shell inherits much of that "Hadoop, but more javascript-y" mindset.

@Aldar 🤦‍♂️
what do you want? Bash commands?

Ask for your money back