3 ms·

At the very least it's useful to use the tools that your coworkers are using. If you're helping a new grad out you do _not_ want to recommend that they use emac

At the very least it's useful to use the tools that your coworkers are using. If you're helping a new grad out you do _not_ want to recommend that they use emacs over VS Code. And, when they have questions about VS Code, it's useful if you can answer them. Maybe you don't have to use VS Code full-time, but having a knowledge of it is useful. Personally, I started using VS Code because support for frontend is much better there than in JetBrains IDEs and it has great remote editing capabilities. I would prefer to use JetBrains IDEs (I did for many years, and I still go back for Java), but VS Code is just better. I would never use Vim for editing full-time, though I do use lunarvim when I need to quickly edit a remote file.

zelphirkalt 2y ago
But I am not the Microsoft support guy, or maintainer of VSCode. It happened in the past, that even though I don't use VSCode, I knew how to help someone, but I would never go as far as endorsing it, especially not to a new grad. If anything in the direction, it would be VSCodium, which the no-carers don't even know exists. Other than that, I would tell them they have to make their own choice and if they happen to choose a tool I know, I can help them out, perhaps. If they want to learn Emacs and ask me questions about how I do something, I would be glad to help them learn this freedom respecting tool, over something like VSCode.