Discussion in 'Business & Enterprise Computing' started by elvis, Jul 1, 2008.
it's an anti-crypto feature. minimises the amount of your data that can be pwned.
yeah love mysql workbench, fuck doing anything via sqlshell!!!!
Fair. And I think the discoverability advantages of a GUI are easily overstated. If GUIs were actually easy and discoverable there would be no Windows XP holdouts...
I suppose VS Code is technically a GUI, so from that point of view I'm a point-and-clicker all day erryday.
Certainly agreed. Not all UX was created equal, and we've all experienced endless menu depth hell.
That, and GUIs immediately get deep into subjective territory. Try designing one and asking for user feedback.
<command> --help == all options and usable methods for thet command, GUI only offers the options programmed into the GUI, and in Windowsland up until Powershell lots of commands had options unavailable to the GUI. Linux GUI options are just as bad.
ask a 5 person team to design a gui and you'll get 6 gui's in return.
Yeah and you can just build a fucking space shuttle yourself too.
CLI Help/man pages without examples of syntax and tasks is cancer.
Seriously go back to help desk.
1) 90%+ of man pages have examples. They're generally at the bottom, which most people never bother scrolling to. This is not a fault of man pages.
2) Install tldr on your servers via your approved configuration management (because it's 2020 and you should have that), and make man friendly for non-sysadmins:
Man pages have saved my ass so many times
Don't pretend you ever left Stack Overflow.
So we require an additional program to help interpret the help files? What does that say about the help files themselves? Nothing right, it's literally everybody else that is the problem?
I'll just wait for Poettering to come along with systemd.mand to sort it out for normal people like literally everything else on this user-unfriendly elitist-jerk-centric clusterfuck that is Linux. Nobody in their right mind would use it in production until then anyway...
Assuming this is an obvious attempt at humour, but I'm 4 beers in and have worked 10 hours today anyway and rolling with it.
Man pages have everything needed. There are even easier options for people who are incapable/unqualified to use what professionals have been using adequately for 30+ years. Open source gives you choice at all skill levels.
Again, rolling with the joke...
brb emailing Netflix/Google/Amazon/Microsoft that they're doing it wrong.
Typical misogynist oppression. How do you expect women to get into IT if everytime they have a question you send them to the man pages?
DW I have already left them a note in our shared (legacy sharing, none of this O365 cloud sharing bullshit) excel document that we use to track issues.
Actually, near as I can tell it's not even that - it's a completely separate repository of example commands, so not only do you now need Internet access from the system where you need the assist, you can't even be sure the examples match your version of the program.
Stick with man and learn to read them. You'll be glad (until you come across one of the fuckers who believe the man page should just be a reminder to use info instead - those bastards can rot).
Edit to add: Everyone who uses tldr gets their own out-of-date-as-soon-as-its-cloned copy of the 22MiB tldr git repo. At least they were smart enough to force it to be found in ~, but I have no idea how it's supposed to update... Obviously this is many times better than a centralised repository, updated nightly by yum/apt/XXXX.
For all of the AS/400 slash iSeries sins, IBM did context sensitive help right with that OS.