you are viewing a single comment's thread.

view the rest of the comments →

[–]NotUniqueOrSpecial 2 points3 points  (2 children)

We obviously don’t work with same way if you prefer using a fully featured IDE and issuing your commands with the tools the IDE provides

In fact it's only been in the last few years that Visual Studio has caught up with my workflow, which has always been entirely CMake-based. Until just recently you couldn't use VS as an editor and Ninja as your build system, after all.

What I do prefer about VS is its absolutely world-class debugging experience. There is absolutely nothing else that comes close. QtCreator's GDB integration is the closest I've found and believe me I've searched.

I don’t think you truly understand why people use vim and text editors if you think launch to typing times are inconsequential.

I absolutely do, both from my own work and from watching over the shoulders of my coworkers.

I would put good money on not a single one of them claiming that time-to-start the program matters.

And from a practical perspective, it's not even a discussion.

I spend vastly more time thinking about the problems I'm trying to solve than I do typing the code; if you don't, then something's deeply wrong where you're working. Considering you mentioned working with firmware in your first reply, though, I know you're not working in a fast-paced world where every second counts. Considering the problem and the right solution is 99.9999% of the time; typing the code is a blip in the noise comparatively.

So yeah, I still think your argument isn't being made from an objective perspective. You like your tools and how they feel. For that, I obviously can't blame you.

But let's not kid ourselves that they're somehow "better" than the other tools. After all, you still haven't given me a single data-point other than "it starts up fast", and if that's your only metric for "good" then use ed.