python < shell (for scripts)
python < shell (for scripts)
Python is the second best language for everything. Having one language that does it all is better than learning several that might do it a little bit better.
35Careful, that attitude is how we ended up with this infestation of JavaScript!
33Speed is a serious problem in Python though. Python has its use cases, and so do other languages. Things would not end well if we started using Python for everything.
8This might be an unpopular opinion but python's speed wouldn't even be an issue if it was 5x slower than it is now.
Python is a language designed for write-time performance, not runtime performance.
2I have worked on a lot of real time simulation with python glue. It is.. not fun. I'm a better programmer for it though.
1If I wanted to write a 3D game engine, I wouldn't use Python either. But there's zero chance of me ever doing that. For 90% of things 90% of people do, Python works just fine. And the performance thing is actively being worked on and getting better all the time.
1
Python is the best "glue" language I've ever used. When you want to chain together your program's high-level logic and all of the loops happen inside lower-level languages like Rust, Go, Zig, D or C, Python's performance is perfectly adequate and it's so clear and concise it reads like pseudocode.
5holy shit you're right
3
Anything I can do in Shell I will do in Shell and yes I am a devops engineer thanks for asking.
29Shellcheck really helps
15
Obligatory relevant xkcd https://xkcd.com/1205/
17Both are
<HTML:
11How to meet ladies?
4sup
1
MFW I'm using sh variant #7923 and trying to write a for loop.
On that other site, I compared it to being a lifelong English-speaking resident of Chicago and being unable to order a pizza in Indianapolis without a phrasebook.
10The only validation you should expect and need is self-validation.
Your work is absolutely valid and important. Your efforts are absolutely appreciated and worthwhile. But people are stuck in their own heads and work and stress and concerns and desires and validation loops and it takes actual work to break out of that to not only offer appreciation but to even realize that they need to offer it.
And for that reason, you should also really appreciate anyone that validates you.
8I know a bit of HTML so I just started learning Python. It's fairly easy and fun, haven't made anything real yet tho
7Things that could have been done in bash is python’s best usecase. And bash sucks for scripting. Why not python?
6There are many cases where bash/shell is better than Python. For one, any time you're just stringing together 2-4 existing shell tools, bash has unbeatable speed since it's all running in C. Plus, you should probably learn the tools anyways to handle CLI stuff on a day-to-day level, so the knowledge is reusable and becomes very intuitive to compose into some crazy one-liner piped chains of commands. If I just want to loop over a set of directories and do a couple chained CLI commands on each directory, this is the way I go.
That said, in cases where you're doing something very custom, any time you're doing something that can't be simply described as a chain of CLI tool transformations, and any time you want to maintain a global state across a complex set of operations outside of a pipeline, I agree that Python is generally a more robust solution with much easier maintainability.
19compose into some crazy one-liner piped chains of commands
Why not something that is completely redesigned from the ground up:
4
have you ever tried to recreate a simple shell pipeline in Python
9If we’re talking about 5 like script, then sure. Just use bash. But python is much better long term, in my experience, for scripts any bigger than that.
-2
Xonsh
1Not really true. Python was created for, and is still best used for data science. It’s user-friendliness made it a first for many inexperienced programmers too, and it started to be used for way more than it was initially intended. I’m not saying it’s bad at everything else, but there’s most certainly better tools for the job.
-8I won’t argue with what it was created for, but I disagree that it’s best usecase isn’t as a bash replacement. That’s the only spot I’ve used and liked it.
2
Groovy is better
5
9
thoughts on lua ?
4Lua is weird, but I would rank it same as Python
5Lua is not as common as python. Every team I've worked on knew X and python. C++, Java, JS, or node, and then also python.
3lua is hot and sexy
3If I have to install it myself instead of being able to assume it's on the system by default, that's a Problem.
2... minimastic iso users: 😐
also i think it comes with neovim
1
I'm using G'MIC for raster-graphic image-processing, but I can do other things in it too with ease. I feel this post so much.
2Python is never the right answer!
1I know there's a lot of downvotes because there are people reading this as hate toward Python. On one hand, one can make the case that it is overused and this doesn't bold well for those that simply can never like it's syntax. On the other hand, Python is perfect for small scripts that isn't tailored for a Domain or just quick codes.
1Honestly, I'm not really a fan of the formatting and syntax of Python but I agree, it is a fine choice for scripting things quickly if you don't mind the language itself.
The biggest issue I have with it are all the incompatible versions, juggling modules, having some other random thing with a ridiculous configuration, where a bash script would be infinitely easier. Anything more complicated and Python is just too much of a headache.
3
They may not know but they will when I explain kekeke
1I can't think of a single reason to use bash over Python. Anything you can do in bash can be done in pure Python. Unless you're working in some embedded environment it's a non-issue to install a Python interpreter (you certainly already have one). I would only use sh/bash for packages I'm distributing to avoid the external dependency, and then only if it's a relatively simple script.
1Bash is much better for doing file operations and piping the output across multiple commands
17Better than subprocess.getoutput?
-1
Why is always about bash? POSIX shell scripts run everywhere.
8Granted, it's a kind of niche use case but in the embedded world there's usually size constraints which prevents a full blown bash installation.
However, things are better now than 20 years ago. Flash is cheap.
2
Python is superior for string anything (parsing, searching, manipulating). But Bash is much simpler for running existing CLI tools. Plus you should already be using Bash as a simple terminal language already, so wrapping what you're used to into a simple script flows naturally.
Eg, if I have some admin tool for updating a user thingamajig, a common scripting need is just running that tool for every user in a file (or the output of another command). The string manipulation that often requires is annoying in bash, but running the commands is easier than Python.
6If what you're doing is essentially a few shell commands, then you may as well put it into a script. If you're talking about how "elegant" your shell scripts are and comparing them to Python, you're probably wrong and should be using Python.
2
This isn't jeopardy! 🤣
1