3 ms·
The point the post makes is valid, trusted, tried and true boring solutions do one thing very well: they are reliable, they work, they ship. But there's a diff
by louwrentius 2y ago
The point the post makes is valid, trusted, tried and true boring solutions do one thing very well: they are reliable, they work, they ship.
But there's a different take:
I've written a lot of bash shell in my life, but at some point I quit and moved over to Python. Having a decent programming language makes building any kind of workflow so much better, easier, prettier, more readable. Anything beyond 10-20 lines becomes Python. Every single time I think 'nah, bash is good enough' I come to regret it.
I wonder if and what the equivalent analogy with PHP is.... ;-)
- internetter 2y agoThe problem I keep hitting is that the standard library of <language> is frequently not as strong as GNU, so then I install a bunch of packages globally and its a mess. Edit: I think there's room for a language with modern control flow that just wraps bash. Like if (true) { cat("path") }
- louwrentius 2y agoA virtual env works fine for this, there's no real reason not to use then in my view.
- internetter 2y agoBut that's a lot more work than a simple bash script
- louwrentius 2y agoPython -m venv dirname . dirname/bin/activate I beg to differ
- Retr0id 2y agoThe boilerplate can be a bit ugly, but you can invoke CLI tools from python just fine. The result is not particularly "pythonic" but I think it beats a pure bash script if there's non-trivial business logic.