A highly customized environment is a timesink of its own, a source of frustration whenever you have to work in a different environment, and 90% of the customizations are pretty meaningless anyway.
Give me reasonable defaults and I'm happy.
Not a knock against VSCode; I acquired this attitude before I started using it. Maybe if I invested in learning VSCode thoroughly, the investment would pay off. I've just been so thoroughly trained not to treat anything outside the terminal as stable that I can't bring myself to do it anymore.
Oh and of course it causes your car to crash constantly now.
I think it was putting work into a vimrc that finally changed my mind. It was great customizing vim, getting it to be just right for myself. But there were a few things that ended up bothering me over time:
* No end state meant I was just constantly toying with it and wasting time. Sometimes the changes would be minor things that barely mattered, but I couldn't decide which way I liked things more * Not always available, leading to needing to essentially remember two different versions of vim. Mine, and the default. * Keybind clashes. Bringing in new plugins was always a pain because there was a good chance that one of my custom keybinds clashed with the plugin, requiring me to make a mess of the plugin's default bindings or to reassign and relearn the colliding binding.
With sane defaults, these problems nearly disappear.
That said there are certain customisations which do really impact my productivity, and they tend to be ones which are 'off the beaten path', so I'm very much in favour of keeping software configurable. There are also tools which I spend a lot of effort hammering into a usable state using their options and extension support, and I wish they would take a more 'toolkit and framework' approach (as opposed to thousands of ad-hoc options), and/or present a more useful default.