Ask HN: Is all programming constantly changing or just front-end JavaScript?
I think much of JS&#x27;s churn has been the problem that the UI primitives (HTML) are unsuitable to what people want to do.  When you can&#x27;t even vertically center something without reading a bunch of web pages that tell you something like six different techniques, you can imagine that people are going to make a library to do make it easy to do.  But since the foundation is crap, and good API design is actually hard, the result is not very good.  So someone tries to fix it later, and runs into the same fundamental problems.<p>I think JS the language is in better shape, but even then it is hampered by poor decisions early on.  (Integer arithmetic done with double-precision floating point underneath the hood?  And it supports bit twiddling, but only if it is really an integer and not a floating point number?  And implicit conversions?  What could go wrong...)<p>But it is also hampered by other problems.  I used WebWorkers recently to compute normals to large amounts of triangles on think, rather than transferring them over the network.  In any normal language, I&#x27;d add a mutex around the data and spin up some worker threads.  But in JS I can either copy the data, or give it away and that thread can&#x27;t access it again.  Since I need the triangle data and don&#x27;t want the hassle of giving it away and then having the WebWorker give it back again (along with the normals), and then having to manage putting it in the right spot, as well as what happens if I need to access triangle data that&#x27;s currently being processed, this is a major pain.  I understand that the WebWorker design makes it impossible for the browser tab to hang on a deadlock or have all the fun threading errors, but as a programmer, JS is the one language that forces poor performance on me.  So you can imagine someone like me, but with more influence, saying, &quot;hey, we need a redesign to fix this.&quot;  But since the previous designers presumably knew how all other languages work and rejected that approach, the redesign probably won&#x27;t really fix the problem, for similar reasons why we didn&#x27;t get WebPThreads the first time around.