its how we roll in Windows land, GUIs over command line mostly

true, you need some screenshots to teach someone a new trick

but then when they've done it once they'll remember it because GUIs really help for that kind of stuff

whereas for command line you'll have to google it every single time for the rest of your life unless its something you do regularly

...Or just commit the terminal commands and/or resulting dotfiles to git.

Which the GUI paradigm has no built in equivalent to

Equivalent GUI paradigm : macro recording?

Not really, at least not in Windows. There are no cross-application macros in Windows, just intra-application ones, and that only for some applications.

It is a little better on MacOS with AppleScript, which can be used to bind different applications together. But not all of them, and it is far from ideal.

In the end, nothing of this is command-line equivalent.

Btw, if you want to see a GUI application that can do really really good macros, learn Blender! E.g. you can bind any button and knob to keyframes to change them in animations. That would be the level of macro-integration required to be CLI-like...

I rather roll with Xerox, Dec, Apple and ETHZ way of computing with OLE Automation, COM, WMI, .NET, VBScript and PowerShell REPLs and scripts.

there's AutoHotKey on windows, among a ton of other automation tools.

Until the UI changes and a button moves or is renamed.