3 ms·

>I’m still frustrated by weird posix incompatibility. Can you also share what are the most significant problems with posix incompatibility for you? Why is it a

• mey 5y ago
  The one I see is really, all of Linux vs OSX/MacOS. And which version of Bash is shipped by default. Internally we have a boot strap run book developers/operations to bring up either Windows/WSL or MacOS to a consistent shell env.
  • preseinger 5y ago
    This shouldn't be an issue! Shell scripts begin with e.g. #!/usr/bin/env bash which means the interactive environment is irrelevant. Users of nonstandard shells like fish need to learn a bit of on-the-fly translation if they expect to copy/paste into their terminals, but it isn't too onerous.
    • mey 5y ago
      Not going to ping my coworker that deals with this (Happy Thanksgiving), but the version shipped with OSX was several versions behind Linux.
      • BigJ1211 5y ago
        I just checked it on my Mac and my Ubuntu server. MacOS has version 3.2.57(1) Ubuntu has version 5.0.17(1) Apparently Apple cites license concerns as the reason for not upgrading it. Don't know how valid that is. License on version 3.2.57 is GPLv2 License on version 5.0.17 is GPLv3+ It's simple enough to update if you use homebrew. `brew install bash` Add the brew version of bash to the /private/etc/shells and change the shell.
        • mey 5y ago
          That's basically one of the developer setup steps, in addition to running through installing things like jq and yq. Point is, it was a significant enough of a delta (easily fixed) that we ran into compatibility issues with the scripts we wrote.
• jscheel 5y ago
  Honestly, I think it’s just fighting years of muscle-memory more than anything. Not necessarily a valid complaint, I know.