Until there's a community for Enterprise Networking you have to suffer my meme.

Documentation too. Frontends change all the time, but CLI tools usually don't, so you can usually rely on old documentation. But have you ever tried googling how to do something in MS office, found and article from half a year ago and found that none of the things it mentions exist anymore? It's ridiculous how much time people waste trying to figure out stuff multiple times because it changes so much.

Depends on what system you’re running, and especially what task you’re doing. Trying to operate firewall rules via CLI is an exercise in self-inflicted pain, as is trying to set a complex cron schedule without a handy calculator.

CLI debuggers can't hold a candle to the Visual Studio debugger. This is generally not something you automate, and I haven't met many engineers that know gdb well. But pretty much anyone can use VS debugger.

IMO GUIs are always faster when it's something you've never used before, or use very infrequently.

CLI is better if you're used to the task you're doing, or automating things. But for infrequent tasks looking up the commands (or looking at old notes to find it) is very slow and rather annoying.

https://xkcd.com/378/

I use both. I use the CLI for a lot of stuff but I also use the GitHub Desktop fork for Linux lol. I don't care how powerful git is in CLI, that gui is just so nice imo

But you look way cooler when using the terminal for most of your stuff 💁‍♂️ also using a riced out window manager and riced out Vim config for which you spent hundreds of hours on customizing every aspect of it :p normal people don't know what the fuck is going on on your pc so you can feel instantly feel superior to those normies! Ah also btw i use arch ;)

Somehow I've made it 7 years without messing up a git command that I couldn't fix in like 2 seconds. I primarily use vscode's source controller more featured source controllers like sourcetree feel overly complex and typing out git commands is fine but you spend more time doing that than you would with vscode's approach. I'm really curious about what you mean by fuck up a commit or push

Yeah, fuck that. It's perfectly fine to build a GUI that makes things a bit easier, but make the GUI so that it resembles the fucking workflow. I hate that when I want to automate something thats super easy in the GUI and it takes AGES because there is no equivalent to what I'm doing in the GUI

One of the best tools I've used is SuperSlicer. It's a slicer for 3D printers. It has GUI, it has CLI and it has a DLL/SO so you can add its features to your own application. And it's open source if linking against an existing library is too hard for you, lol.

Why not mount your server as a share and use your desktop GUI to manipulate files? Then you can do both.

I always feel that graphical interfaces make easy things difficult, in most cases. A bunch of figity clicking around, instead of a few keystrokes I could press with my eyes closed. They are more discoverable, though.

If you use emacs, dired and wdired together are fantastic for managing files like that. You can even run dired over tramp, so you can manage files on a remote server that doesn't have emacs installed, using the emacs on your desktop. But there are also good cli options, you might want to look at the rename command, as one that's probably installed by default on any given distro. That's outside my expertise, though, as I just use emacs.

Skip the masochism, try helix. Switched to that + zellij with about 20 lines of config and never looked back

So far I don't think anyone has interpreted the meme correctly, the wikiHow guy is supposed to be an obvious shortcoming expressed as a guy trying to convince himself it's not a problem.

thank you.

It's been a while since I've found that true. You can do everything you want to do in powershell now days.

First of all, most Windows settings are in the registry, so you don't have to go to the UI, you can just upload new settings straight into the registry through CLI.

Second, PowerShell exists and it's awesome!

And third, you can always use UI automation tools if you're bad at registry and PowerShell. Just record your session and run whenever needed.

Newer versions of Windows can give you the exact Powershell code it's executing based on what you've configured in the gui. This is still extremely inconsistent across Windows services though. I don't know that I'd feel comfortable running a headless windows server yet. Too much stuff still assumes you'll use the gui for most things.

I just walked around my house touching all my mirrors and they all do this. Hope they're not on to me now... Think I'll wait for night and try to make a break for it.

Or it's an extremely thin glass.

Searching a log file? I want less. Searching all log files? I want log aggregation lol.

Github's UI is total garbage compared to basic git commands, though.

"Windows engineer' lmao.

👍👍👍 arch btw 🤤🤤🤤 I use arch btw 🥺🥺🥺 you 🫵🫵🫵🫵🫵🫵🫵 should use arch too btw 👄❤️ I used to be a filthy 🤮 windows 🤮 user 🤮 but now I use arch!!! 🤤🤤 don’t be afraid of the install process, you’re just a dumbass normie 🤓🤓🤓🤓

Exactly. Posting to a community of a dozen people who don't engage on content seems like a pointless endeavor.

Cisco and Juniper CLIs are terrible imo.. Why won't they just use a proper modern set of tools instead of their own proprietary shit that doesn't interface with anything else?

So much GUI, and never a mouse click. Only the best hackers get a whole new screenfull of GUI for every one of their seemingly random key presses.

To be fair. In Star Trek they're not really using a GUI like we use a GUI today. They are using a high level AI to take voice commands. And they use the visuals to confirm. That is not what gooies are today

And now the timeline is forked.

Here is an alternative Piped link(s): https://piped.video/watch?v=LkqiDu1BQXY&

Piped is a privacy-respecting open-source alternative frontend to YouTube.

I'm open-source, check me out at GitHub.

I don't know how fair it is to use Cisco as an example for a GUI.

The CLI is like magic words, and a GUI is like Dr. Strange magic with your hands waving around.

In my experience, CLIs are easier to design but harder to design well. Because of that, when I find a good CLI tool it runs as smooth as silk, but I would easily take a decent GUI over a shitty or rushed CLI.

And can be automated easily.

What is this thing you call “good gui”?

Mine is Ubuntu. What it says is "I installed it years ago because it was the one I knew most about but now very much regret doing so."

At some point I'll have time and switch. Maybe go with Mint or Debian. There's way too many things that randomly break and it's become rather laggy over time.

Right? I'm fully capable of using docker compose. But portainer adds an easy and useful admin layer to it.

I've written a pretty big application for my employer in visual studio. Never once have I run a "dotnet build" command. Only ever used the little play button. Guess I'm no software engineer

The real software engineers are those who can 2 minute Google "how to build with cli" their Hello world console app.

I absolutely love using git on the command line. I'm comfortable with the commands, and there isn't much need for clicking since a lot of it is just typing commands, viewing files/diffs, repeat until files are staged, committed, and pushed up. Who needs a GUI for that?

OTOH, I really like postman for constructing and templating network requests. There are a few helpful panes and forms that just fit better on one screen that I can interact with.

To say working with GUIs makes someone a worse engineer sounds very short sighted to me. IMO the best engineers are the ones who use tools that maximize their efficiency.