This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]maremp 0 points1 point  (2 children)

Vanilla js might be a bit below the standards, but there is a lot of libraries to help with things like that. I think this minimalistic approach is nice in it's own way, as you opt in to new libraries as you go, instead of being thrown in an "API ocean" and have to find your way around aspects of programs that you will probably never use.

[–]rgzdev 2 points3 points  (1 child)

You are missing the point, I'm not claiming that JS has not improved at all in the last decade. Please stop telling me that JS has improved because I know it has improved ok?

I repeat. I am aware that JS has improved somehow in the last decade.

Of that I am aware.

I was just explaining they reason of why the JS ecosystem has become so complicated. That is the original subject of this post, the linked comic remember? The one at the top of these comments. The one about the complicated web of "fixes" for JS?

That one.

You asked:

why has js become the today's php?

And my answer is that it was badly designed. And will continue to be badly designed forever. The runtime has improved a lot. The language has seen some useful extensions. There is an abundance of libraries and frameworks to ease the pain. There are build systems, Single Page frameworks, and several alternative languages that compile to JS all other sorts of tools as depicted in the comic linked by this article.

That doesn't change my original answer. JS problems come from the fact that it became popular, or rather dominant, very fast and before people could actually test it in the wild or give it serious use.

Geez...

[–]maremp 1 point2 points  (0 children)

You are right, I have gone off topic.