view the rest of the comments
Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
Vi/vim is honestly a horrendous tool. It's nice if you want to spend a few hours memorizing commands and learning how to use a text editor. Then you can do cool stuff.
But it very much shouldn't be the default tool for anything really.
In any OS published some time within the last two decades you'd expect a decent GUI settings tool to handle all that work for you and if you really need to sudo a text config file it should at least by default launch a GUI text editor for that purpose when running in a graphical shell.
vi/vim/nano/emacs are ok for CLI only setups, but there's no point to have any of that as defaults or even recommendations for graphical sessions.