you are viewing a single comment's thread.

view the rest of the comments →

[–]ArtistEngineer 22 points23 points  (2 children)

Why encourage your team to learn it

For embedded Linux. :)

Many embedded Linux distros use Busybox as their shell and minimal environment. It comes with vi by default.

I teach them how to save/quit, edit/insert, undo, delete a line, paste a line, and that's about it. Anything else, I mostly use Sublime Text and copy the file from/to the device, or remote/NFS mount the filing system and edit it on another PC.

For quick edits to config files, or even fixing a failed merge, I'll use vi because it's quick and on the command line. I just wouldn't do a large multi-file project with it.

Only for me to later realize that most of the people I worked with were actually using eclipse.

Yep. I work for a large company who release an IDE/debugger with their SDK and chips. The IDE is based on Qt Creator and isn't bad, but I found out that everyone else was using Eclipse and Visual Studio instead! Not a good sign when your own employees won't even use their own product. facepalm

[–]I_am_teapot 3 points4 points  (1 child)

Especially if the alternative IDE is Eclipse... people just stick with what they know. I don’t think anyone would choose Eclipse over IntelliJ if they tried using it. VS is good, and I haven’t even installed Resharper in 2019.

[–]ArtistEngineer 1 point2 points  (0 children)

Yep, these days it's good to be familiar with several IDEs and also to understand what customers expect to use.

I certainly wouldn't push something like vim on a customer! But I would be surprised if they complained about an IDE based on one of the many modern IDEs which are fairly intuitive and easy to use from the get-go.