In what way is it restless?

Listed under advantages in the article: "State lives on the server. It is not memoryless request-response: there is a process per connected client that remembers where it is. It is the opposite of htmx, which is deliberately stateless."

▲

nchmy 2 hours ago | parent [-]

but if state lives on the server and all you are delivering is html, how is that not "restful"?

	▲	frollogaston 2 hours ago \| parent [-]
		One of the main properties of REST: "Each request from any client contains all the information necessary to service the request, and the session state is held in the client." In practice, REST makes things like caching, load-balancing, and debugging easier at the cost of needing to send more state back and forth. In HTTP, there are ways to reduce or at least hide the repeated TCP handshakes.