Is this something that should be mitigated or avoided, or is it just the cost of progress? Is there a particular part of the ecosystem offering stability and fast progress?
Create templates to quickly answer FAQs or store snippets for re-use.
Both good and bad. I think the fast-moving ecosystem does bring fresh ideas and progress, which is good. I think this could be bad because it doesn't always seem to build on previous parts of the ecosystem. The progress isn't always moving things forward, but creating adjacent progress. Instead of enhancing or creating the next iteration of an existing tool, new tools are created from scratch. Angular/React/Vue/Svelte all serve the same purpose at the end of the day, they are just different ways to do it. Same for Express/Koa/Hapi/Fastify/etc.
The large leaps forward for me were:
I think those things are innovative and worth the disruption to stability/comfort. Switching from Framework A to Framework B is harder to justify as worthwhile when they do the same things but are more preference-based.
There are ends of the spectrum.
"Move fast and break things" is a great motto for trying new things, but trading stability for velocity often has terminal side-effects, like killing longevity or product maturity.
Think of all the potential Devs that Google alienated with the use of this philosophy with Angular 2-6.
Production and enterprise systems need to work with products that have that maturity and stability, otherwise they get passed over with little thought.
I think general it is a good thing, it means new ideas are being tested and implemented consistently instead of stagnating. However, after a few years it can get really exhausting.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.