The Biggest Lie In HTML
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Related videos
This is bad...
Theo - t3․gg
104.3k views
I’m done.
Theo - t3․gg
185.8k views
Get In, We're Leaving GitHub
Theo - t3․gg
137.1k views
I’m serious.
Theo - t3․gg
95.7k views
OpenAI is lying
Theo - t3․gg
81.9k views
I was wrong
Theo - t3․gg
69.3k views
I can't believe he was right.
Theo - t3․gg
64.4k views
I’m so tired.
Theo - t3․gg
65.4k views
GPT-5.2 is the best model ever made*
Theo - t3․gg
100.4k views
Is gpt-5.1 the best code model ever?
Theo - t3․gg
63.2k views
Top Comments (10)
The web is built on a mountain of tech debt.
Something about an issue being "Library does the thing it's meant to do completely wrong" is really amusing to me
I went to MDN to see the list of self-closing (which they call Void Elements) and they indicate that the /> is invalid HTML. I clicked on embed, one of these elements and the example had the invalid />. 😂
Enters HTML, the programming language
As someone building it’s 100% the fault of the framework creator. If you’re building a language wrapper it’s YOUR job to fully understand the details, especially the fine ones, of the language that you’re wrapping. It’ll be like building a C++ framework with a pointer object that is actually a reference under the hood.
<div /> Hello Will always look like an error for me.
If only we had a tool to show the browser what language version we’re using so it could parse accordingly… you know, like doctype and head meta tags 🙃
I was one of the XHTML proponents. But it had one huge problem on every browser that even supported it (at least it did back in the day): a single syntax error made the browser shit itself and refuse to render anything. But in my opinion they threw the baby out with the bathwater. They could have made HTML5 xml-like and xml compatible while also making it fault tolerant like it is today.
Theo's "Just never write html" argument misses the point.
I handwrite HTML for work. Also, my personal website doesn't use any framework, just handwritten HTML, CSS, and a tiny bit of JS.
Unlock the Data Inside
Turn Videos into Knowledge
- Get FREE 10/day: transcripts, summaries, chats
- Chat with videos, export text & PDF
- $1 free API credit for RAG, chatbots & research
Free forever plan • All features unlocked
Top Comments (10)
The web is built on a mountain of tech debt.
Something about an issue being "Library does the thing it's meant to do completely wrong" is really amusing to me
I went to MDN to see the list of self-closing (which they call Void Elements) and they indicate that the /> is invalid HTML. I clicked on embed, one of these elements and the example had the invalid />. 😂
Enters HTML, the programming language
As someone building it’s 100% the fault of the framework creator. If you’re building a language wrapper it’s YOUR job to fully understand the details, especially the fine ones, of the language that you’re wrapping. It’ll be like building a C++ framework with a pointer object that is actually a reference under the hood.
<div /> Hello Will always look like an error for me.
If only we had a tool to show the browser what language version we’re using so it could parse accordingly… you know, like doctype and head meta tags 🙃
I was one of the XHTML proponents. But it had one huge problem on every browser that even supported it (at least it did back in the day): a single syntax error made the browser shit itself and refuse to render anything. But in my opinion they threw the baby out with the bathwater. They could have made HTML5 xml-like and xml compatible while also making it fault tolerant like it is today.
Theo's "Just never write html" argument misses the point.
I handwrite HTML for work. Also, my personal website doesn't use any framework, just handwritten HTML, CSS, and a tiny bit of JS.