In the defense of framework writers a los of these CSS frameworks appeared at a time when there were vast browser incompatibilities. Today browsers have standardized a lot but a decade or so ago they were vastly incompatible in key areas.
So for example jQuery didn't only make it a bit shorter to write, it also saved you to some degree of having to worry so much about IE incompatibilities. The same goes for some of the other frameworks of it's time.
And Typescript is more about bringing static typing to the browser.
But I definitely agree that too many decisions are being made out of fashion choice rather than true technical merit. And there seems to be a compulsive need to follow the "new best thing" all the time. It seems unhealthy for the industry to me.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
In the defense of framework writers a los of these CSS frameworks appeared at a time when there were vast browser incompatibilities. Today browsers have standardized a lot but a decade or so ago they were vastly incompatible in key areas.
So for example jQuery didn't only make it a bit shorter to write, it also saved you to some degree of having to worry so much about IE incompatibilities. The same goes for some of the other frameworks of it's time.
And Typescript is more about bringing static typing to the browser.
But I definitely agree that too many decisions are being made out of fashion choice rather than true technical merit. And there seems to be a compulsive need to follow the "new best thing" all the time. It seems unhealthy for the industry to me.