@jbz BTW, I can't say that a commands' flags and arguments are a big pain in ass. If user switches from GNU utils, which uses a lot of GNU-specific things, to the BSD utils, which doesn't adopt various GNU things – then it's strange to wait for the same arguments of commandline utils, even if they named the same.

It is like the heavy user of Windows cmd.exe switched to Linux and disappointed that "commandname /?" doesn't show the help message to him.

Those days, when I first time tried FreeBSD, I had a lot of shell scripts full of Linuxisms in my dotfiles. Yes, I was need to spent some time in editor and remove all Linux-specific things from scripts — but now they able to run in both OSes

The biggest thing was to rewrite scripts to use a proper shebang – not the Linux-specific "#!/bin/bash", but the much more portable "#!/usr/bin/env bash":

https://codeberg.org/evgandr/dotfiles/commit/0da26c8efd367d50a6cf0d7df6a835121cef21eb

https://codeberg.org/evgandr/dotfiles/commit/dd34bf8a4f437a76b5da4b23c0f84aa13766d8e7

#BSD #FreeBSD #Linux #shell

@jbz

I relate to the gripes about command line flags, but not at all about the community.
At least on the #Fediverse, the #FreeBSD community has been wonderful. The #BSD community overall has been absolutely great.

I mean, just look at the number of people who only run BSD on servers, and run either windows or more likely macOS on their personal machines. I've never seen any of them derided or gatekept, even when I myself felt like slipping in a little "why ain't'cha dogfooding it, brah?" comment here or there. 😅