JavaScript isn’t the problem. Replacing the browser was.
August 11, 2025
We spent a decade rebuilding the browser by hijacking routing, manually syncing state, rebuilding forms and transitions in JavaScript to match native app expectations. Now the browser has caught up. It’s time to stop the hacks and build on the web again, but properly.
Source: JavaScript isn’t the problem. Replacing the browser was. | RedwoodSDK
The era of heavy client-side JavaScript driven frameworks may be coming to a close. Despite their shortcomings, there were very solid reasons for this approach.
But those reasons with the maturity of the web platform and features like view transition and speculation rules mean that many of the reasons for these architectural choices are no longer as significant.
As Peter Pistorius observes:
We can finally stop fighting the browser. We can stop re-implementing it. And we can start building on top of it, natively, progressively, and with confidence. JavaScript isn’t the problem. Replacing the browser was.
