Ask HN: Fatigued by the complexity of ES6 tooling. What to do?
I just don&#x27;t use any tooling and&#x2F;or needless abstraction. It&#x27;s not necessary at all, just like it was not 6 years ago. I write ES5-only code if I need to target IE9+.<p>I still don&#x27;t get the appeal of virtual dom. Browsers already have DOM, why use another crippled parallel one? It can only cause trouble and increase cognitive load when trying to do anything fancier.<p>I understand the value of having state in one place and being able to call some function to update the UI to match the state. But that is a separate concept from virtual DOM.<p>You can do a lot of useful stuff with real DOM, actually leveraging the power of prototypical nature of Javascript. Store your own data in it, add your own methods, etc.<p>I don&#x27;t get much JS fatigue. Perhaps because I&#x27;m working in a bubble and don&#x27;t feel the pressure to adopt the latest tech quickly.<p>Recently I had to extend fairly complex HTML-only web app that I wrote 11 years ago for a client, and it was quite fun. It&#x27;s sort of nice to see that, while it&#x27;s fun to write SPAs and everything, there are still ways to write web apps without a single line of JS.