Earlier quoted context omitted.
>>Just timed it myself, started and ready to go in 120ms. Let me get this straight. You plan to code for hours, and your biggest concern at this point in time is your editor takes 1 - 2 seconds more to start? A second is 1.666666666667% of a minute. And 0.02777777777% of an hour. Just how much more productive are you getting by saving this time? On the other hand emacs is notorious for making users spend days to get…
Programmer brains are weird, and are stimulated thoroughly by any and all optimization, especially ones that are impossible to not see On the scale of reality, it's obviously less time to just pick up VScode in a few hours of learning (if that), and then deal with it taking 2-3 seconds to launch But on the scale of programmer brain, it's clearly wayyyy better to invest days into learning emacs, writing custom configs…
If you are writing html, css, react, js, python, sql and myriad other things. Then having all of this configured to your likings is a multi month project. While vscode gets you up and running in minutes.
Edit efficiency should be least of your worries. vscode constantly reminds me if I forgot to import something, or if I imported something and forgot to use it. It lets me navigate code semantically, not just through text tags. It lets me debug, have a project running on a remote box, and let me work on it like Im working locally etc etc. Writing a full feature list will make this a blog post/book.
At the end of the day my job is write code, not to work on side tooling projects.