1224
Claude Code deletes developers' production setup, including its database and snapshots — 2.5 years of records were nuked in an instant (www.tomshardware.com)
submitted 6 months ago by to c/technology@lemmy.world
289 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 1 point 6 months ago (2 children)

Quite true.
It's an argument I often have with the CLI only people, and have been having for years. Like 'with this Cisco router I can do all kinds of shit with this super powerful CLI'. Yeah okay how do I forward a port? Well that takes 5 different commands...

Or I just want to understand what options are available- a GUI does that far better than a CLI.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 6 months ago (1 child)

    IMO it's important to recognise that both are valid in different scenarios. If you want to click through and change something that's actually doable with a couple of clicks, that's fine. If you want to do this through the CLI, it's also fine - if you're someone who's done 10 deployments today and configured the same thing, it would be muscle memory even if it's 5 commands.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 2 points 6 months ago

    Quite true there is absolutely a place for both in all situations. And it's why I hate absolutists who think gui's are some sort of disease. GUIs are discoverable and intuitive, You can lay out all the options for the user so they know what they can choose and make the right choice. CLIs are powerful and scriptable, easy to automate.
    Neither is bad.

  • permalink
  • fedilink
  • source
  • parent