Comment by zamalek

Comment by zamalek a day ago

2 replies

I coincidentally watched BasicallyHomeless's video on his 100+ day Linux experiment and he made a really good point: because everything on Linux can be done with the CLI, it also has a working natural language interface (Claude Code). He ran into several issues, such as sound (allegedly that's no surprise, but not my experience), and Claude fixed them all.

If it doesn't wipe your drive.

Still, interesting thought.

kristofferR a day ago

Yeah, setting up my router with VLANs/Firewall/NAT etc was so damn frustrating with Ubiquiti compared to the Mikrotik router I had before.

While I could just export my config file with Mikrotik and ask ChatGPT to make whatever changes I wanted in seconds ("here's my config, make a vlan 20 with all my iot devices") and get a fully working config back, with Ubiquiti you just get a bunch of inaccurate "click here and there" instructions back instead since the UI changes slightly all the time.

The switchover was still worth it, as the Ubiquity UI is nicer in daily use (and Mikrotik wifi sucks ass, so I had to use other APs). However, every time I want to change something I wish I had an easily ediable config file to edit, and get LLM help with, instead of a confusing UI to click around in.

  • nine_k a day ago

    With OpenWRT, it's likely even easier :)

    Indeed, large language models have much easier time working with a real written language.

    I wonder if the modern GUI conventions could be reliably translated to machine-understandable text representation, operated on, and then mapped back to the GUI picture.