HTML over WebSockets: real-time SPAs with barely any JavaScript

Aug 12, 2026 · 4:51 PM UTC ·10 min read · 0 reactions · 0 comments · 4 views

#html #websockets #real-time #spas #barely

TL;DR · WeSearch summary

It is an accepted, professionalized scenario. But being a standard does not make it the only way. I want to show you another approach, one that is not new but has gained traction over the years: HTML over WebSockets.

Key facts

▪It is an accepted, professionalized scenario.
▪But being a standard does not make it the only way.
▪I want to show you another approach, one that is not new but has gained traction over the years: HTML over WebSockets.

About this source

Hacker News (Front Page) files mainly under programming. We currently carry 1,484 of its stories. Top-voted stories on Hacker News.

All Hacker News (Front Page) coverage →

Original article

Andros

Read full at Andros →

Story provenance

Source · retrieval · rights · ranking — open for full record

inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisher	Andros
Canonical URL	https://en.andros.dev/blog/ef4968f5/html-over-websockets-real-time-spas-with-barely-any-javascript/
Publication time	Wed, 12 Aug 2026 16:51:25 +0000
Retrieval time	2026-08-12T17:16:35.161Z
Last seen	2026-08-12T17:16:35.161Z
Headline source	Publisher (no WeSearch rewrite)
Excerpt source	publisher body
Excerpt method	First ~120 words (~800 chars) of extracted publisher body, fair-use limited.
Summary	WeSearch · cerebras-chat (WeSearch summarizer)
Summary source text	contentText
Citation coverage	Summary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Cluster	Wc6dhZqZZhRc · 1 stories
Cluster logic	Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reason	Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visit	Yes — open original
Substitutes article?	No — link-out required for full text

Rights status (four layers)

Publisher-declared

No publisher-confirmed rights record for this source yet.

Machine-readable

No source-specific machine-readable restriction detected beyond the public feed.

WeSearch interpretation

WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.

Unknown

Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing	May the item be indexed (stored, ranked, made findable)?	Allowed
Snippet	May a short excerpt of the publisher's text be shown?	Allowed
AI summary	May WeSearch generate its own short summary of the article?	Limited
Retrieval / RAG	May the content be exposed for third-party retrieval-augmented generation?	Not asserted
Model training	May the content be used to train AI models?	Not asserted
Commercial reuse	May the content be reused commercially?	Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Open original publisher → Source rights JSON → Machine-readable provenance → Rights framework → WESEARCH-STORY-PROVENANCE-V1

Opening excerpt (first ~120 words) tap to expand

HTML over WebSockets: real-time SPAs with barely any JavaScript web javascript python django websockets django liveview Leer en español Share Building a SPA (Single-page Application) is a complex puzzle: a JavaScript framework that draws the view, an API serving JSON, and 2 independent codebases forced to understand each other through contracts. It is an accepted, professionalized scenario. But being a standard does not make it the only way. I want to show you another approach, one that is not new but has gained traction over the years: HTML over WebSockets. The idea is this: instead of sending JSON and assembling the HTML in the browser, the server sends the HTML already built and the client just places it where it belongs.

…

Excerpt limited to ~120 words for fair-use compliance. The full article is at Andros.

Anonymous · no account needed

Discussion

0 comments