Connect to Wi-Fi from CLI in Linux
|
|
|
Comments (4)
You've just summed up the wrongness with current GUIs: unless the designer thinks of what you want to do, you can't do it.
This is opposed to command line interfaces, where if you can think of it, you can do it. I believe this derives from the fact that a CLI has a grammar. You can describe things in a language with grammar that you can't in the rebus of a GUI. Given the correct type of grammar (generative in the philosophical jargon), you can describe new things, things un-conceived of before.
That's where we want to be, in possession of a generative interface.
This is opposed to command line interfaces, where if you can think of it, you can do it. I believe this derives from the fact that a CLI has a grammar. You can describe things in a language with grammar that you can't in the rebus of a GUI. Given the correct type of grammar (generative in the philosophical jargon), you can describe new things, things un-conceived of before.
That's where we want to be, in possession of a generative interface.
Some GUIs are excellent, with a logical flow and organization, and some have 'view log' buttons, and places to enter custom CLI options. Those are three GUI features I wish were universal.
Hey! Glad it helped!
Post a comment
A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.
Your message:Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help
Sign up and post (it is free) or Log in and post

Some Linuxes use dhclient instead of dhcpcd.
My gripe against GUI config tools, like Network Manager, is they work one way, and if that fails you have no way of debugging and figuring out what went wrong, or alternate options to try. It seems the trend is to make them more limited, instead of more capable.