Hacker News Reader

It’s always been easy to reactively update the DOM. I was doing that in vanilla JS before HTML5 had been formalised.

What the frameworks do is take this concept one step further to create a SPA (single page application) but I honestly think they’re an antipattern that needs to die.

View on HN

The problems are ownership and provenance mainly, and that all DOM access is slow and requires syncing code internally.

Anyone can write code that tweaks nodes or uses templating, but doing it in a consistent way on a project with hundreds of thousands linea of code is challenging, especially if you also need performance and everyone's least favourite child: accessibility.

Sure you don't get some of this with frameworks, but they help a lot.

Well yeah, obviously frameworks are intended to provide a standard interface for projects that scale. But you’re describing a different problem to the one originally argued.

Reply on news.ycombinator.com