Wesley Aptekar-Cassels | There is no such thing as a static website
A common distinction in technology for building websites is a separation between "static" and "dynamic" websites. The idea is that a "static" website always returns the same HTML/CSS/etc, whereas a "dynamic" website changes the content that the server returns depending on the request.
A common distinction in technology for building websites is a separation between "static" and "dynamic" websites. The idea is that a "static" website always returns the same HTML/CSS/etc, whereas a "dynamic" website changes the content that the server returns depending on the request. This seems, at first glance, to be a pretty sharp and useful distinction, letting us easily distinguish between static and dynamic. However, I don't think it holds up to real scrutiny, and I believe that this distinction is holding us back from building better types of software that exist in the blurry space betw
saved by
related reading
- How to Build a Personal Webpage from Scratch – Alex Rutarrutar.org
- How to Host a Static Website with Nginx | by Jason Rigden | Mediummedium.com
- The new wave of Javascript web frameworksfrontendmastery.com
- Web Applications 101 - Robin Wieruchrobinwieruch.de
- Wesley Aptekar-Cassels | Consider SQLiteblog.wesleyac.com
- How to make a static websitedennisc.net
- No, dynamic type systems are not inherently more openlexi-lambda.github.io
- The Descent — What Happened to the Frontend While You Weren't Watchingdavidpoblador.com
- Extensible Software in the age of LLMs | Jeremy Morrelljeremymorrell.dev
- Why I Have a Website and You Should Too · Jamie Tanna | Software Engineerjvt.me
- unhosted web appsunhosted.org
- CDNs aren't just for cachingjvns.ca