Git - the Github Desktop application is a great example of how easy git could be for users like me who only rarely use git. Every time I need to do somethign other then a simple pull or push I need to look it up and by the time I need it again I have forgotten the command and need to look it up again. Just give me something like Github Desktop on linux
this post was submitted on 22 Jul 2024
87 points (94.8% liked)
Linux
48331 readers
630 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
Lazygit, beautiful, terminal based, runs everywhere
Lazygit
Thats pretty good, thanks.
Anything that needs to be configured with YAML, and Kubernetes in particular.
I mean I get the whole Infrastructure as Code hype (although I have never witnessed or heard of a situation where an entire cluster needed to be revived from scratch), but it should be very possible to make a gui that writes the YAML for you.
I don't want to memorize every possible setting and what it does and if someone makes a typo in the config (or in the white space, as it's YAML) everything is borked.
Call me old-fashioned but the graphical ui of something like octopus deploy was a thousand times more user friendly imho.
That UI is called VSCode
At the top of your .yaml file, you can set a JSON Schema. Example:
# yaml-language-server: $schema=https://json.schemastore.org/prometheus.json
scrape_configs:
- job_name: caddy
static_configs:
- targets:
- caddy:2019
This way, you don't have to memorize every possible setting and what it does and risk making a typo in the config. VSCode will just tell you.
I think infrastructure as code is best utilized when paired with software testing and rapid deployment. It allows for a kind of granularity manual configuration doesn't give you
A few IDEs already provide some help with YAML. Rider will tell you if you've screwed up the YAML for a GitHub Actions workflow, and possibly docker-compose as well
I think it’s easy to make a generic YAML editor that all you need to do is to pass a “definitions” file that says all the possible options to show as a drop down or toggle etc.
That would be useful for many projects.
I'm missing a good GUI to manage SELinux. It is probably because I don't know how to handle it but I hate this thing with passion.
A single, decent, maintained one for LVM.
Redhat had a couple of goes at this and they suck ass big time and rely on KDE (so no good for any other DE / WM). I'm not sure anything really works, so I'll say: none exist.
There's no CLI that k wish I had a GUI for, but there's many GUIs for which I wish there was a CLI version.
The cli controls the computer while the GUI controls the user
Not at all.They are 2 ways do the same thing. The GUI can tell you what options are available. The CLI needs you to memorise them, or go somewhere else to look them up.
A lot of GUIs have less options available than their CLI equivalents. Moreover GUIs change more often, requiring you to relearn the actions to get the expected result Shells can remember the commands you used, commands are also way easier to write down on paper than a list of actions to do on a GUI And using man or --help is not going somewhere to know the options, you stay in the shell If you want to know all the features of a tool, reading the manual is also easier than browsing all the GUI
The CLI lets the user automate tasks, giving them more control over their workflow
GUIs can have just as many options. Sure there are programs with poor UX. Choose a good one. There are also many GUIs with no CLI alternative, or only a poor UX alternative. As the GUIs guide the user, small changes are understood right away. GUIs remember last settings all the time. Great for reuse. If you have to write a command down, for GUIs it need not be perfect. For CLI one letter wrong and it fails. Using man commands is yet another command to learn and does not work with all CLI commands. It is possible to automate GUI commands.
And even if there was some benefit to a CLI, the entire UX is so poor you can understand why most people prefer GUIs. It's the dominant way for good reason. And why most CLI users use a web browser and GUI email client.
Why would i use something so restrictive as cli tools when i can change the data directly with assembly?
The whole CLI. Linux should automatically generate default GUIs from manpages and code, to be developed further by the crowd of users on the desktop. It's pointless to handcraft both interfaces one app at a time.
I like Linux Mint (compared to Ubuntu, Debian, and Windows) because usually right-clicking takes me closer to the solution I'm looking for, but it doesn't allow me to dig deep enough. It should be discoverable all the way from the desktop to what makes it tick. Think of Smalltalk by Alan Kay in Xerox PARC in the 1970s, or what it would be now had it been mainstream all this time. #discoverability #explorability
That would probably look terrible though.
view more: next ›