The problem for me is keeping up too. Say I'm creating a back end system and I think it'll be nice to implement a nice web based GUI on top of it. I know HTML and CSS and am quite capable of crafting something nice. So I take a look at what I need to get a quick HTML/CSS baseline in there with a CSS preprocessor. I want to make sure this GUI is modern enough that it's easy to maintain going forward. So I have a Google to see what I need. And most of the time it tells me I want...
And so on. Before I know it I've got this mismatch of tools that installs all kind of configuration files in my project & enforces a directory structure I don't really need either. I've often started done the route and thought, screw this. Downloaded the dependencies myself, compiled the CSS myself and been much happier!
So the point of my waffle - if it's awkward enough for something experienced then yes - it's gone too far. It's fine for tinkering, side projects, quick prototypes etc. But for a stable product, you'd have to question if it's worth it at times.