@lispi314@samir Yes. It was ultra light ajax and basically the first major site to use it to have replies and other actions have immediate effect on the page rather than having to do a klunky reload.
@lispi314@samir Then they rewrote it entirely as a client side web app where all the rendering, rather than changes by user action, were implemented in js with lots of round trips to server and a heavy client side data model outside the DOM. It's completely analogous to difference between how a shell with readline works vs how curses works.
@lispi314@samir Google did a similar rewrite to Gmail around the same time with exactly the same effects. Went from fast on 2006 hardware to painfully slow on much later hardware, and worse UI.
@lispi314@samir It's really a shame that this isn't well documented anywhere, only existing in the memories of folks who experienced it. I wonder if copies of the js they served back then ever got saved anywhere...
@lispi314 @samir Then they rewrote it entirely as a client side web app where all the rendering, rather than changes by user action, were implemented in js with lots of round trips to server and a heavy client side data model outside the DOM. It's completely analogous to difference between how a shell with readline works vs how curses works.