Back-end languages are coming to the front-end
What&#x27;s incredibly frustrating about the knocks on JavaScript is that it&#x27;s not a shortcoming of the language that creates the problems hinted here, but the poorly-considered engineering choices of the popular frameworks.<p>After building my own framework [1] last year, I realized just how disconnected JavaScript developers—yes, the &quot;big boys&quot; are especially off in CS la-la land—were from web development fundamentals. HTTP distilled down to its absolute essence is brilliant, but for some reason gets absolutely ignored in the JS world. When you couple that with websockets for incremental updates (similar to what Chris McCord is doing in Phoenix), it&#x27;s insanely powerful. It can be reasonably lightweight, too, if you&#x27;re only shipping the JS you need to render the page.<p>That rendering some HTML, CSS, and interactive JS in a browser has been turned into what it has is staggering. Though, not surprising, when you realize a lot of the momentum in JavaScript the last decade or so was perpetuated by venture capital (and the inevitable fast and cheap nature of that world) being pumped into inexperienced teams.<p>[1] <a href="https:&#x2F;&#x2F;github.com&#x2F;cheatcode&#x2F;joystick" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;cheatcode&#x2F;joystick</a>