Spas Are Just Harder, and Always Will Be (2013)
Single Page Applications (SPAs) offer a great user experience but come with significant development challenges. They require an additional logic tier compared to traditional web apps, complicating the architecture. Additionally, data synchronization issues can arise due to the larger amount of data stored in the browser, making it harder to manage stale data.
- ▪SPAs require three tiers of logic instead of two, adding complexity to development.
- ▪The architecture necessitates handling data presentation in both the web server and browser tiers.
- ▪Data synchronization can be challenging in SPAs due to the risk of stale data in the browser.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
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 | William Gross |
| Canonical URL | http://wgross.net/essays/spas-are-harder |
| Publication time | Sat, 23 May 2026 09:24:10 +0000 |
| Retrieval time | 2026-05-23T09:37:26.609Z |
| Last seen | 2026-05-23T09:37:26.609Z |
| 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 | 5kgc_TX5sH4v |
| 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)
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.
Opening excerpt (first ~120 words) tap to expand
April 4, 2013 William Gross SPAs Are Just Harder, and Always Will Be April 4, 2013 William Gross There's quite a lot of talk these days about Single Page Applications (SPAs) and the terrific user experience they deliver. This is great, and the SPA architecture is probably a good fit for many apps, but I want to point out two reasons why SPAs are harder to develop and maintain than traditional server-side web apps, and why they will always be harder regardless of new JavaScript frameworks and other technologies that become available. If you're considering a SPA architecture, remember to weigh this additional difficulty against the user-experience benefits you'll get.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at William Gross.
Discussion
0 commentsMore from William Gross
