As a side note, this can be a good thing. When a certain amount of change aversion isn't maintained, you get change for change's sake. Organizationally, you get every new manager trying to "make their mark" on things. Individually, you get developers trying to add "migrated product to $X shiny new framework" to their resume for their next job hop in 2-3 years.
But many/most of us have probably also worked in environments that were far too conservative about changes, so that may be the more common problem.
But many/most of us have probably also worked in environments that were far too conservative about changes, so that may be the more common problem.