this post was submitted on 05 Feb 2025
100 points (99.0% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
62215 readers
283 users here now
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Rules • Full Version
1. Posts must be related to the discussion of digital piracy
2. Don't request invites, trade, sell, or self-promote
3. Don't request or link to specific pirated titles, including DMs
4. Don't submit low-quality posts, be entitled, or harass others
Loot, Pillage, & Plunder
📜 c/Piracy Wiki (Community Edition):
🏴☠️ Other communities
FUCK ADOBE!
Torrenting/P2P:
Gaming:
💰 Please help cover server costs.
 |
 |
|---|---|
| Ko-fi | Liberapay |
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Not OP, but I always prefer bash over python since it's "lower level". But that's just a preference.
I'm with this... Bash runs in nearly anything without any real good chance of version conflicts.
Why complicate things needlessly?
That's profoundly untrue. Scripting in bash is an indescribably painful experience.
You have absolutely no idea what version of a binary the user will be running so you're limited to using only options that have been well established.
I've never worked with python but I understand it has at least got some semblance of package management providing assurance that methods you're calling exist, and I imagine it has some standardised mechanism for handling errors unlike bash.
A simple example is making a GET request to an API and deserializing a JSON response if its successful, handling a timeout if the server can't be reached or handling the HTTP status code if it's not a 200 response.
JS, python, Rust, C#, Java etc will all handle that simple scenario with zero effort but in bash it's a nightmare.
POSIX and shell functions can get us very far indeed. At least, not everthing's an object in Bash. :P