If you're using a GUI, that means whatever you're doing you're not doing a lot of it, since you don't need to automate it. I would expect a world-class enterprise engineer to be able to automate most tasks, and from that they would be very comfortable with the command line.

Can you do everything with a GUI that you can on a command line? Yeah probably, if the developer is at all the features properly. Can you automate it easily? No not at all. So the more you do something the more you tend to want to deal with the vocabulary of the command line because it's more expressive and allows for automation.

I will die on this hill!

[–] Newusername4oldfart@lemm.ee 25 points 1 year ago (3 children)

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.

[–] ysjet@lemmy.world 9 points 1 year ago (1 children)

on the contrary, CLI is the BEST way to deal with firewall rules.

[–] Lodra@programming.dev 6 points 1 year ago

Personally, I'd take it a step further. Firewall rules should be defined as code in a git repo. So if you're building rules in a gui, you're simply doing it wrong. While a cli and/or api should be used, that should be automated and invisible to a human.

[–] Rakn@discuss.tchncs.de 2 points 1 year ago (1 children)

TIL there are people configuring firewalls via GUIs. Okay … I‘m do that too on my private equipment because I’m lazy. But it feels wrong doing so in an enterprise context.

[–] Newusername4oldfart@lemm.ee 2 points 1 year ago (1 children)

You using a Cisco firewall or something?

[–] Rakn@discuss.tchncs.de 1 points 1 year ago

I’ve been using F5 in the past. Not doing that anymore though.

[–] baascus@lemm.ee 1 points 1 year ago

Junos CLI is a real treat. I work with the SRX line regularly, particularly the SRX4600 and the SRX300 series.

load more comments (10 replies)