@fluffy *the ideal

frigging English

@chimerror pure client-side statefulness? ugh

@chimerror I mean that's not 'a web app' that's an app that runs in a browser

@fluffy well usually any JS is extremely limited for such apps. There's no state to keep because you're not really pulling much from a database you just display a web page at an url.

rather than a list of recent articles being grabbed with Ajax, for example, it will be determined when the website is built, and just be written out in the final HTML.

State is strictly limited to stuff on the client side like themes or cookies.

@fluffy it's basically how it was supposed to be before JS or the server became *the* place to put all logic.

No logic, no need.

@fluffy here's the repository for an old version of my website done this way: https://github.com/chimerror/ChimerrorProductions

When I want to add a new article, I check it into the repository, and then the site is built and redeployed, and that's it. little need for JS.

@chimerror I think we might be talking cross-purposes

What you have isn’t a “static web app,” it’s a website. Which is the way most websites should be.

I really really dislike the appification of the web.

@fluffy ah! I completely agree!