Skip to content
loading...

re: Is a "fast moving ecosystem" good or bad? VIEW POST

FULL DISCUSSION
 

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:

  • jQuery -> React-like frameworks.
  • Browser JavaScript -> being able to run it server-side with Node.js.
  • Disparate REST endpoints -> GraphQL.

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.

code of conduct - report abuse