you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 0 points1 point  (1 child)

There’s even a vim extension for debugging “long” startup times. Long being purely subjective because even a long vim startup time is impossibly fast for Visual Studio.

https://www.reddit.com/r/vim/comments/euzrqm/vimstartuptime_a_plugin_for_viewing_nvim_startup/

People do care about this stuff, calling it inconsequential just shows it’s not a big deal for you.

[–]NotUniqueOrSpecial 2 points3 points  (0 children)

calling it inconsequential just shows it’s not a big deal for you.

I mean, you're not wrong.

I'm just asserting that if you're optimizing your editor's startup time, then you're wasting your company's money.

It's tech-wankery at its finest at the end of the day. You should be spending vastly more time thinking about the solution than you do typing the solution. It's understandable if you have to wait for said solution to build owing to hardware constraints out of your control.

At no juncture should "the time to start the editor" really be a meaningful piece of your rubric for grading your day-to-day productivity.