I'm usually running about ~4 instances of it locally in separate Git worktrees, which (in our setup) means I'm also running 4 copies of the whole stack: web, frontend, Redis, Postgres, etc. These are rebuilt and torn down multiple times per day. Lot of frontend assets to compile.

Additionally, like many people in corporate environments, we do of course also pay a performance tax thanks to the security software we need to run.

So perf does matter for us.

We could, of course, alternatively... just run cheap shitboxes locally and have all our dev environments in the cloud. Certainly appealing in many ways from a cost perspective and you don't even need to give up DX really.

However, in the next ~5 years, as "actually useful" local LLM inference starts to become genuinely useful (for software engineering, this seems to roughly mean "the ability to run 28B+ models at usable speeds") then having local compute horsepower might start to look more attractive again. Even if it's not an absolute winner on cost/utility alone, the data privacy and cost certainty have value to many.

I feel like a big part of macos slowing down is installing too much crap over the years that sits in the background.