It’s relevant. From about 1995 to 2006, Microsoft was pretty much hard set on ‘cli is dumb, do nothing cli wise, cmd is a concession, but a crappy one’. As an artifact of that, you got regedit, a godawful ‘GUI’ that took a messy datastore model and just kept it ugly, in a way that would have been pretty much better as a CLI interface.
Microsoft started getting the idea again, but in true Microsoft fashion, had to reinvent the wheel and did PowerShell to try to create a CLI ecosystem from scratch rather than trying to build anything vaguely familiar. To their credit, for first party stuff they did a fine job enabling it, though third party applications remain a mess to this day. It does highlight that even Microsoft figured out that CLI actually does make sense a lot of the time.








To the extent that is true, then the novice doesn’t end up asking for help. The goal is that the capability is discoverable. Or if it’s really a bit harder, there are hopefully tutorial youtube videos that cover the use case.
But when a user asks for specific help on a task they couldn’t figure out for themselves, or are asking for help with a ‘something went wrong’ dialog box, well helping with CLI is much more feasible than the involved mess of trying to basically make video tutorials ad-hoc, or screen share, or try to help them find the obscure log file an application wrote somewhere with the real error.