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.
view the rest of the comments
I think these two talks by Chris Toomey sum up pretty well everything that is nice about vim:
If you've used vim for a while now and feel a bit stuck, they bring you to the next level and are pretty straightforward.
That said, other editors also have their pros and I've become a bit tired of looking for the most efficient one or so. It really doesn't matter in my job if I need x hours or y hours to write something (although vim probably scores well there). I use it nowadays mostly because it works well for me, it feels kind of fun, it doesn't eat my computing resources, and it's here to stay (free).
Thank you for the resources, I'll try them once I get the chance to work on a project for awhile again. The reasons why you like it are great to hear, as many videos tend to focus on speed over other aspects. If speed was my only concern I could have stayed with an IDE which I knew how to use. For me vim is both exciting to learn as a skill and convenient because of it's server friendly interface.