> Markdown version of [/videos/1291-using-all-the-html-running-state-of-the-browser-and-modern-is-rubbish?t=4015](https://www.wearedevelopers.com/videos/1291-using-all-the-html-running-state-of-the-browser-and-modern-is-rubbish?t=4015). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Using all the HTML, Running State of the Browser and "Modern" is Rubbish

AI coding agents risk building a generation of illiterate programmers. Ditch over-engineered JavaScript platforms and embrace the native web platform using built-in APIs and semantic HTML.

- **Speakers:** [Chris Heilmann](https://www.wearedevelopers.com/@chris-heilmann), [Daniel Cranney](https://www.wearedevelopers.com/@daniel-cranney), David Letorey
- **Event:** WeAreDevelopers LIVE
- **Published:** January 29, 2025
- **Duration:** 1:15:44
- **URL:** https://www.wearedevelopers.com/videos/1291-using-all-the-html-running-state-of-the-browser-and-modern-is-rubbish

## Summary

The convergence of historical web infrastructure and new AI challenges highlights a unique transitional phase for developers. With recent events demonstrating how easily digital reality can be blurred, version control has proven essential by operating as a tangible record of truth to track unacknowledged content changes. Alongside this, the rapid adoption of AI coding agents like deepseek and devin raises concerns about cultivating a generation of illiterate programmers; by focusing strictly on output, developers risk losing foundational problem-solving skills and defensive debugging capabilities, essentially accepting failing code simply because a machine generated it. Instead of chasing these hollow shortcuts or relying on what marketing vaguely rebrands as "modern" tooling, developers are urged to embrace the evolving stability of the native web platform. As native solutions aggressively replace over-engineered JavaScript platforms—proving that "the web is winning"—developers can now leverage built-in capabilities like the popover API, CSS nesting, and upcoming Tailwind 4 attribute functions. Furthermore, after decades of struggling with Java-derived legacy behaviors, the upcoming JavaScript temporal API finally resolves systemic date and time manipulation issues. Retaining foundational knowledge extends directly into inclusive design and accessibility. Adhering to the principle that the first rule of ARIA is to not use ARIA, teams construct resilient interfaces using semantic HTML forms rather than fragile, div-heavy architectures. Thoughtful UI implementation also requires addressing neurodivergent realities, such as understanding that all-caps text destroys semantic word shapes, constructing visual rectangles that severely hinder dyslexic readers. Community-driven initiatives and independent browser projects like Ladybird continue to dismantle web monoculture, redirecting the developer ethos toward accessible, secure, and thoughtfully crafted web standards.

**Keywords:** version control tracking, ai coding agents, deepseek integration, devin testing capabilities, javascript temporal api, native web platform, semantic html architecture, aria accessibility rules, css nesting, tailwind 4 attribute functions, popover api, dyslexia web accessibility, ladybird browser engine, rss feed management, web standard specifications, mdn documentation search

## Chapters

1. **Tracking website changes using version control tools** (04:46) — How public source code repositories act as living records of governmental policy shifts.
1. **Preserving deleted content through the web archive** (09:38) — Why caching services are critical for maintaining the historical record of abandoned web projects.
1. **Hypocrisy in artificial intelligence data scraping practices** (12:02) — How large language model providers complain about unauthorized data usage while relying entirely on scraped content.
1. **Generative artificial intelligence and programming fundamentals** (13:37) — How relying on automated code generation might erode essential problem-solving skills for incoming developers.
1. **Combining language models and communities for problem solving** (25:19) — Why querying real developers in specialized chat communities often outperforms automated debugging assistants.
1. **The problem with claiming technologies are modern** (31:37) — How labeling frameworks as modern creates fleeting relevance and litters search engines with outdated tutorials.
1. **Replacing algorithmic social media feeds with real syndication feeds** (36:11) — Why returning to direct content subscriptions provides better signal than engaging with automated engagement algorithms.
1. **Improving accessibility for icon buttons and vector components** (37:55) — How missing text labels on standalone iconography excludes screen reader users and obscures application functionality.
1. **Utilizing cascading style sheet attribute functions in Tailwind** (39:03) — How consuming data attributes directly in styling frameworks reduces the need for constant script-driven utility generation.
1. **Relying on native markup elements over generic containers** (40:53) — Why selecting inherently semantic tags avoids the constant need for complex accessibility declarations.
1. **Participating in the web standards specification process** (45:19) — How developers can formally submit proposals for desired platform features instead of complaining on social media.
1. **Replacing legacy date objects with the temporal application interface** (47:43) — How native timezone awareness within the browser execution engine finally eliminates reliance on fragile external date parsing libraries.
1. **Security risks in web interfaces for automated vehicles** (51:57) — Why integrating remote locks via exposed browser endpoints leaves physical assets highly vulnerable to hacking.
1. **Frustrations with boilerplate syntax in web component designs** (56:02) — Why repetitive scoping declarations deter adoption of native encapsulation methods among interface engineers.
1. **Disabling integrated artificial intelligence assistants in operating systems** (58:11) — How to manually remove unwanted generative text features that are forcefully installed on productivity machines.
1. **Formatting text safely without impacting screen reader accessibility** (60:09) — Why transforming casing through style sheets preserves native readability for differently-abled users compared to scripted text mutations.
1. **Automating dynamic copyright years in footer components** (64:12) — Finding amusement in over-engineered deployment packages solely designed to render the current twelve-month period.
1. **Attending web standards and browser history community events** (66:55) — Previewing upcoming opportunities to witness the unveiling of an entirely independent rendering engine in local engineering meetups.

## Related Moments

- [Advocating for semantic HTML over complex framework component workarounds](https://www.wearedevelopers.com/videos/1753-wearedevelopers-live-spicy-vanilla-web-css-magic-more) (from "WeAreDevelopers LIVE – Spicy Vanilla Web, CSS Magic & More")
- [Navigating web element APIs and emerging software vulnerabilities](https://www.wearedevelopers.com/videos/1362-wearedevelopers-live-our-world-congress-2025-code100-highlights-with-jack-barber-and-marco-podien) (from "WeAreDevelopers LIVE - Our World Congress 2025 & CODE100 Highlights with Jack Barber and Marco Podien")
- [Adapting modern web architecture for artificial intelligence crawlers](https://www.wearedevelopers.com/videos/1287-chatgpt-vs-google-seo-in-the-age-of-ai-search-eric-enge) (from "ChatGPT vs Google: SEO in the Age of AI Search - Eric Enge")
- [Audience questions on accessibility and framework tradeoffs](https://www.wearedevelopers.com/videos/459-extending-html-with-web-components) (from "Extending HTML with Web Components")
- [Navigating accessibility standards and screen reader support limitations](https://www.wearedevelopers.com/videos/1806-nolojs-avoiding-javascript-cruft-with-html-and-css-aaron-t-grogg) (from "NoLoJS - Avoiding JavaScript Cruft with HTML and CSS - Aaron T. Grogg")
- [Addressing browser support for legacy capabilities and modern frameworks](https://www.wearedevelopers.com/videos/647-defeat-that-legacy-monster-guerilla-refactoring-with-web-standards) (from "Defeat that legacy monster! Guerilla refactoring with web standards")

## Related Articles

- [Dev Digest 133 - Back to Front](https://www.wearedevelopers.com/magazine/474-dev-digest-133-back-to-front)
- [The Web We Broke (And Why AI Agents Are Paying the Price) - AgentCon Berlin](https://www.wearedevelopers.com/magazine/735-the-web-we-broke-and-why-ai-agents-are-paying-the-price-agentcon-berlin)
- [Dev Digest 116 - WWWAI?](https://www.wearedevelopers.com/magazine/449-dev-digest-116-wwwai)
- [Dev Digest 128 - Do not Google Monopoly](https://www.wearedevelopers.com/magazine/465-dev-digest-128-do-not-google-monopoly)

## Related Jobs

- [Remote Senior Full-Stack Engineer](https://www.wearedevelopers.com/jobs/ext/679408-remote-senior-full-stack-engineer) at **Edge Impulse**
- [Remote Senior Full-Stack Engineer](https://www.wearedevelopers.com/jobs/ext/683045-remote-senior-full-stack-engineer) at **Edge Impulse**
- [Remote Senior Full-Stack Engineer](https://www.wearedevelopers.com/jobs/ext/639235-remote-senior-full-stack-engineer) at **Edge Impulse**
- [Remote Senior Full-Stack Engineer](https://www.wearedevelopers.com/jobs/ext/645320-remote-senior-full-stack-engineer) at **Edge Impulse**
- [Remote Senior Full-Stack Engineer](https://www.wearedevelopers.com/jobs/ext/682327-remote-senior-full-stack-engineer) at **Edge Impulse**
- [Remote Senior Full-Stack Engineer](https://www.wearedevelopers.com/jobs/ext/646086-remote-senior-full-stack-engineer) at **Edge Impulse**