Our industry is beset by chasing the shiny. It happens on all sides of the house, development, operations, support...and it's deadly. Yes, if a new tool comes along that obviously blows the old tool out of the water absolutely it should be investigated, and time taken to really dig in and see what the warts are.
I've done Fortune 50 team development and lone wolf development. While the needs of the two are vastly different (lone wolves must be DevOps by definition, Fortune 50s not so much) neither one has time to chase the shiny-of-the-week. So much of our industry is exposed to what amounts to snake-oil salesmen that talk a great game but deliver so much less. Worse, they do it to managers who are all too often divorced from the trenches.
I'm in the enviable position as a lone wolf to be required to choose which tools I pick up. After forty+ years in the game I've become absolutely ruthless about the new shiny. Because I'm doing the work of developers, operators, DB admins, etc. my primary focus becomes is this new shiny going to shoulder some of my workload?
ModelRight does that. Redgate's SQL Toolbelt does that. Visual Studio and Crystal Reports and SSMS do that. And do it while letting me keep my (pitiable) budget from falling over.
You got a new shiny? Cool! Let me scrounge 15 minutes from my frantic workday and look it over. Will it do anything that saves me enough time to justify the hurt it puts on my non-existent budget? Ok, I'll go beg my boss for however much pain he's willing to endure from his boss.
It won't? Don't let the door hit you on the way out, you Sales Weasel!