Are frameworks converging? Lets explore the topic of carcinization within the web development world, and can we glimpse what the future holds, by looking back?

Jacob Kofoed

Venture Capital

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

Web frameworks are converging towards a similar set of features, including immutability, single-directional flow of data, signals, and server-side rendering. Predictions for the future include resumability and wider adoption of web components. The proliferation of frameworks has led to a clearer understanding of browser needs and the potential for framework-like capabilities without the need for a full framework.

The carcinization of web frameworks

I always think that old client/server is more interesting and stable than full client side app with an API.
But yes, web components are really interesting and I like to manipulate it, with or without shadow dom. They are really good, but downloading all the resources on client’s device is not the best thing to do in my opinion.
Just because we are approaching almost unlimited power/storage does not mean we should abuse it. The most we process back, the cleaner the user will understand how your app works, and the most satisfaction you’ll have.
But I could be wrong…
(I’m currently using angular on several projects, and I’m learning flutter, but that doesn’t mean I’ve successfully understand how toddle works…)