@jibal We are very off topic here already, but anyway. I try to be less offensive now. That is not very professional. The problem that I have with javascript is, that it rules the web. Languages that compile to JavaScript have to be aware of the fact that they compile to JavaScript. When I write a program in for example Go, and one part of my program is compiled to JavaScript, I have write this part differently than the rest, because it is compiled to JavaScript. Just to give an example, passing value types in Go is probably just a memcopy, on the JavaScript backend it will create this heap object that might cause the garbage collection cycle to kick in. This is exactly what I think what the problem is. There are even a bunch of languages evolving that are desinged around the fact that they compile to JavaScript, just because compiling to JavaScript is such a different task than compiling to the typical x86 binary. I don't want my programming language to behave differently, just because I am compiling it to the web. I want my uint8 to be exactly one byte, and not a float64 that behaves like as if it was an uint8. My prediction for the future is, that as soon as we have that, JavaScript will stop growing, and very very slowly but steadily go back. It will disappear like Cobol, not at all. But it will loose relevance in projects that do not have a JavaScript history. It is not just me, people don't want two very differently behaving systems. That is the reason, why node.js is so popular, they just decidid that everything should be javascript. I will not come to that side, I think nothing should require JavaScript.
By the way I am not a web developer. I write 3D game engines. I live in a very different Bubble than Web Developers do.
