> End users don't want complex UI interfaces It's complex UI requirements, not complex UIs... For ex our company routes phone calls and needed routing system

> End users don't want complex UI interfaces It's complex UI requirements, not complex UIs... For ex our company routes phone calls and needed routing system that had 3 layers deep of hierarchical organization, reordering, sorting, weighting, grouping etc. You could have done all of those with a new page load every time, or spread out into individual static pages, but that'd take 10x longer for the user. I built something that did all of that in a box that fit into one screen and one page load, and only 1 ajax request for autocomplete search box. Some things just demand 'desktop style' complex browser UIs that server side simply can't provide... Which is why every serious company that makes $$ uses it. Backend devs like to pretend they can throw the baby out with the bath water and call it day, then deliver poor UX because they limit themselves artificially, just because some people abuse JS. That's not the solution.