We've been using web sockets for a period of time now but we are changing course back to old-school server-side HTML with basic form posting. There simply aren'

We've been using web sockets for a period of time now but we are changing course back to old-school server-side HTML with basic form posting. There simply aren't any user interactions in our product that justify the additional complexity of having a web socket connection involved for every users' session. I've observed an interesting pattern - When we started to take the axe to web sockets (and all the reasons we thought we needed them), a lot of javascript seemed to melt away pretty quickly. We still require javascript, but it's exclusively in service of the UI/UX at this point, not some self-serving SPA framework state management circus.