You mean a chat cliënt? That seems a good worse case scenario.

If you limit history to the most recent message (and have an link to the archive at the top) you could simply reload the entire page on some interval that declines with message frequency (and when you submit the form)

Since the html document is pretty much empty the reload happens so fast you won't see the flashing. With transitions it would be perfectly smooth.

With modern css you can put the elements out of order. You can simply append the new line to the end of the html document that represents the channel. (And to the archive) Purging a few old lines can be done less frequently.

I haven't tried it but it should work just fine. I will have to build it.

Initial load will be 100x faster. The page reloads will be larger but also insanely robust.

▲

nemothekid 4 days ago | parent | next [-]

>You mean a chat cliënt? That seems a good worse case scenario.

No, I mean discord. An application where you can chat, recieve phone calls and watch a live stream all at the same time.

A pure html chat client is uninteresting - there have been realtime html chat clients since I was teenager, even before the release of jquery.

	▲	econ 4 days ago \| parent [-]
		The things I was wondering about were: 1) can a non spa chat client be as good as a spa. 2) at what point is a spa justified. (is chat enough?) Phone calls and live streams are things for which a tab needs to stay open. If you want to do other things simultaneously both the browser and the OS could facilitate it - but do so rather poorly. It's not why people make spa's it seems?

▲

albedoa 4 days ago | parent | prev [-]

> You mean a chat cliënt?

Calling Discord "a chat cliënt [sic]" is barely one step removed from "I could build that in a weekend". So go ahead. Wait, what is stopping you?

	▲	econ 4 days ago \| parent [-]
		No audience.