> If you want anything more than a static site The problem, as always, is (poor) developers making poor decisions. Implementing static sites as a JS-required,

> If you want anything more than a static site The problem, as always, is (poor) developers making poor decisions. Implementing static sites as a JS-required, JS-heavy pages is something that some poor development teams are doing. Bungie, game developer, have been replatforming their site and they've turned what is mostly static content pages into purely client-side single page app which requires javascript to display anything https://www.bungie.net/7/en/Destiny/BeyondLight https://www.bungie.net/7/en/Destiny/BeyondLight It's sad because there are extremely productive ways to build this out using their preferrred technoligies (react) but deliver the static content from the server in the initial page load AND continue doing SPA-style navigations if desired. --- There are lots of webpages out there, that means there's lots of developers making them. Some developers will be good, some will be average, and some will be bad. The 'problem' with websites is that it's a lot easier to see when they've been done poorly, compared to say native apps.