JavaScript is a rollercoaster. From "Golly hello world is easy and I can make webpages now", to "wtf '1'+1 is '11' kill me now", to "it's not be that bad if you know how to use it", to discovering typescript and it starts feeling like a real language.

... until you can't build the project because you have too many types so you blow the memory limit in node. I can up the limit, but I can't guarantee that we won't blow past this in the future. Browsing issues on the ts repo reveals that this has been a thing for years.

Sticking with the rollercoaster analogy I'm now at "Burn it all to the ground".

I'm starting to get what's the deal with all this JS train... Almost every goddamn time there are contributors and maintainers that force close issues that have not resolved the premise. One can argue that same thing applies to developers using other languages and that these have lesser amount of frameworks to seriously rely on, but I've grown weary of seeing ultra confident JS devs that assert the problem is solved and issue discussion only keeps growing because it is actually some reoccurring problem. And to keep sponsors on their side, of course, they would try their best to prevent further discussion, which is the path of convulsive resistance to accept facts.
Just one of the reasons we have so much libraries now. (Though I'm trying to not lighten up fuss around absurd atomic libraries.)

@vintprox Also not JavaScript, but you reminded me of this snip I came across the other day

@ltlian Oh my, these subjects have lost fear entirely.
What do we do with this, by the way?

The more I look into js the more I understand why web assembly started to be a thing..

@LotsOfCaffeine Well, I'm sure there would be alternative proposed and promoted sooner or later, otherwise Consortium without innovations would make no sense and be a subject to constant public pressure.
Being tightly attached to JS monopoly for too long is no go.