Huh. SPAs are "static"?

Remember when "dynamic site" meant that a website includes JavaScript? That's what "D" in "DHTML" was for. JavaScript.

· · Web · 1 · 1 · 0

@temporal in a sense of you can call them static. But the person writing that likely didn't know and just stumbled on the right terminology.

A static web site has no logic on the server side. So my KAP implementation running in the browser would be a static site.

@loke Right. I'm not even criticizing, just noticing an interesting inversion of meaning.

Back when I started with webdev, an SPA would be the definition of a "dynamic site" - in the DHTML sense, using JavaScript to make the experience interactive without server round-trips. What happened on the server was out of scope.

Fast-forward almost 2 decades, now "dynamic" means "markup generated on the server at request time" and implies server state; static means downloading cached markup and no server state.

@temporal I think we've had two full reversals and returns to previous meaning.

Recall that the first sites were completely static (just fixed pages served from a server). The first move towards more dynamic sites were CGI scripts and the like, dynamically generating content on the server.

Later, the pages became dynamic (meaning interactive), and after that you had the dynamic client code communicating with the server using XMLHttpRequest. Finally there was the shift towards single page applications.

All of the tösen changes in some way redefined what static vs dynamic means.

Sign in to participate in the conversation
Mastodon for Tech Folks

This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!