3 ms·
I would argue, however, that the situation for shells is even worse, as: 1. The version of bash is even more out of date (Dating back to 2007 on current macOS
by microtherion 5y ago
I would argue, however, that the situation for shells is even worse, as:
1. The version of bash is even more out of date (Dating back to 2007 on current macOS releases).
2. #!/bin/sh Could give you any one of a number of slightly different shell implementations.
3. The differences between Python versions are clearly documented, and, while painful, possible to work around. The differences between shell versions can be far more subtle and more difficult to discover.
4. You not only need to deal with the shell version, but the version of every tool you use as well.
- devenvdev 5y agoI would argue that in practice, the only difference between implementations was an inconvenience to me was on Mac - I have to use gsed instead of sed, etc. Everywhere else, it's pretty much consistent from the one-liner user POV. On the other hand, I occasionally encounter different python versions, which always includes some mental effort to tune in.
- microtherion 5y agoWhat kind of ecosystem are you operating in outside of macOS? If you're operating in a Linux monoculture, I'm sure your experience is quite realistic, but historically, there were several different sed's (of which the fact that macOS uses BSD sed by default is a reminder), several awks, several bourne-like shells (some of which still exist, optimized for either better interactivity or smaller footprint).