The demise of the mildly dynamic website (2022)

Original Article ↗ Hacker News Discussion ↗

Serverless platforms, heavyweight JavaScript frameworks, and static-site/CDN setups are displacing the old model of “mildly dynamic” sites built from a few PHP or CGI scripts on cheap shared hosting. Commenters weigh the trade-offs between today’s managed, auto-scaling, pay-per-use infrastructure (like AWS Lambda and Cloudflare Workers) and the simplicity, durability, and low cognitive load of FTP-and-PHP-era workflows, noting that modern stacks often add complexity, maintenance churn, and vendor lock‑in. Many argue that for small or personal projects, shared hosting, basic PHP, or static hosting with light client-side JavaScript still offer the best balance of cost, security, and ease of use.

Lambda, CGI/PHP, and “mildly dynamic” pages

  • Many argue Lambda’s core appeal (give code a URL, scale to zero) is conceptually similar to old CGI/PHP, but with cloud billing and automation.
  • Others push back: CGI/PHP still require an always-on server you maintain, while Lambda bills only when code runs and auto‑scales across a cluster.
  • Several note that Lambda’s practical complexity (API Gateway, IAM, VPC, limits, cold starts) is far higher than “drop a PHP file on a server.”

Ops burden, security, and maintenance

  • One camp says self‑hosting is easy: minimal hardening, occasional apt upgrade, maybe unattended upgrades; uptimes of years are common.
  • Critics counter that “years of uptime” usually means missed security updates, growing exploit risk, and eventual painful OS/API deprecations.
  • DDoS and spam (especially on comment sections) are cited as modern threats that push people away from running their own dynamic stacks.

Cost and scaling tradeoffs

  • Some emphasize how cheap traditional VPS/bare metal is, especially at scale, and cite large companies saving big by avoiding clouds.
  • Others argue that for side projects and low-traffic apps, Lambda and similar services often cost effectively $0 and remove sysadmin overhead.
  • Concerns are raised that autoscaling FaaS can turn a DDoS into a catastrophic bill, though WAF and rate limiting can mitigate this.

Static hosting, CDNs, and “mild” dynamism

  • Many participants have migrated to static sites (S3+CloudFront, GitHub Pages, Cloudflare Pages) for near-zero maintenance, low cost, and strong resilience.
  • Dynamic features are often offloaded to third‑party services (Disqus, analytics, OAuth) or implemented as client-side JS hitting APIs.
  • CDNs are seen as a big driver of static-first design; mildly dynamic behavior is layered on via JS or edge functions.

Frameworks, JS vs PHP, and complexity

  • Some lament that simple one‑file PHP scripts have been replaced by heavy JS frameworks and brittle toolchains.
  • Others argue modern JS frameworks plus managed hosting are actually less overall work than maintaining LAMP stacks, especially for teams.
  • Debate over vendor lock‑in: proponents say code is mostly plain JS and portable; skeptics point to provider‑specific IAM, networking, and services.
  • A niche defends old-school PHP/CGI (and even SSI) as still viable for small, long‑lived mildly dynamic sites; others never want to touch PHP again.