So many JS frameworks, but why?
Tags: frameworks, webdev, javascript, astro
Published: 2024-06-26 20:24:45

We can often think that it’s already disgusting how many frameworks there are on the market, or think that some people have been left off the technology train and are on their way to being out of a job soon.

_Why is it that every day a new technology is born that changes the method and way of working with web interfaces?_

The simplest reason is that it is difficult to add or change certain features to established frameworks.

As Fernando Herrera commented in his weekly podcast “Devtalles”, all new frameworks come out with the intention of including something new, in addition to starting from a good code base that can scale and implement some techniques that allow them to be more efficient and take up less space and resources. **Incredible, right?**

**Although, honestly you ask me which one I consider has done better, and I would answer Astro.**

Why Jose???👀

> _So many frameworks that have implemented cool and ingenious functionalities that have even been implemented in the most used frameworks, or those same frameworks are looking for a way to implement their own solution to not stay out of the trend.
> And for you only Astro has done it right? Exactly!😉_

Other frameworks have included valuable features to mention, as did SolidJS with the signals that everyone wants or has (even already on the way to standardize on ES). Qwik with resumability capability, absolutely stunning reduction of Javascript when loading a website, and so on and on and on.
What’s up with all this?

The only thing I see, in my opinion, is that they have worked hours and hours with the intention of presenting something new and attracting attention, only for big frameworks to pick it up and implement it. And they create the framework only with the intention of having somewhere to run these new features.

It doesn’t look like they intend for their framework to be the one used.

Moreover, everything seems to be caused by lack of communication between developers, envy and selfishness with which they just want to get something first and have their name mentioned. So that they can take a place in history as the developer of that feature and not be in the shadow of a team.

The most serious factor for them is in npm libraries. For React, Angular and Vue for example, there are libraries with all kinds of solutions. You want to implement something in your system, you search a little bit and there it is, a library to solve it.

Now, I challenge you to find such a solution for new frameworks. Before you get tired of searching, better take that time and create something yourself, so you contribute to the framework community and learn new things😉.

This weak point does not allow the mass acceptance of every new framework we see, because a company is not going to allow itself to redevelop hundreds of features that already have libraries that they use in their projects. Just to use this new technology to reduce time, add something new or be trendy.

_That’s why we see banking systems of yearssssss still using Cobol, but this is another topic._

And this is where you ask me, Jose, where is the one you say was the best idea at the time of creation? Oh yes, you are talking about Astro, this one will be pending for the next blog (I don’t want to extend so much, sorry😅).

**_Each week I will bring interesting and varied content, developmental, personal, whatever comes to mind. Support this content to keep getting the best of it!🍀_**