> because waiting for the car to warm up takes a few minutes.
If only it was this. Usually the car transmission breaks, there are random engine shutdowns, and after restart the car just doesn't function anymore. And when it actually does start, it moves so slow and consumes so much fuel that I can't justify using it. That's my experience with JetBrains IDEs.
Side note: to a rounding error, all modern cars can be safely driven right away. Wait a few seconds for the sound of the engine to change, indicating that oil is now happily pumping through all the grindy bits, and then you're ready to go. I'm not saying you want to drag race your neighbor 10 seconds after starting the engine for the first time that day, but once you don't hear the tappets being tappety, it's OK to pull out of your driveway and start moving at a sane pace.
Not who you are replying to, but the new Lexus RX350h takes and absurdly long time to be ready to drive away, if you want to use the rear camera to help back out of the parking lot.
If a text editor is a car, an IDE is an airplane. You can get to more places with it, but you need a lot of space and time to even start moving and then it consumes a ridiculous amount of fuel.
That actually makes it a great analogy. An IDE allows you to make common edits like renaming a variable, just as an airplane gets you to any big city. But when you need to make an uncommon edit, it’s better to reach for Vim – just like you need a car to get to some random place in the middle of woods.
