Transcript for Dan Houser: GTA, Red Dead Redemption, Rockstar, Absurd Future of Gaming Lex Fridman Podcast #484
This is a transcript of Lex Fridman Podcast #484 with Dan Houser. The timestamps in the transcript are clickable links that take you directly to that point in the main video. Please note that the transcript is human generated, and may have errors. Here are some useful links: Go back to this episode s main page Watch the full YouTube version of the podcast Table of Contents Here are the loose chapters in the conversation. Click link to jump approximately to that part in the transcript: 0:00 Episode highlight 1:17 Introduction 3:03 Greatest films of all time 15:16
Could not retrieve the full article text.
Read on Lex Fridman Blog →Lex Fridman Blog
https://lexfridman.com/dan-houser-transcript/?utm_source=rss utm_medium=rss utm_campaign=dan-houser-transcriptSign in to highlight and annotate this article

Conversation starters
Daily AI Digest
Get the top 5 AI stories delivered to your inbox every morning.
More about
version
The Real Size of AI Frameworks: A Wake-Up Call
You Think You Know What You're Installing When someone says "just install PyTorch," you probably think "how bad can it be?" It's a deep learning library, right? A few hundred megabytes, maybe? Think again. I built pip-size to expose the hidden cost of Python packages. And what I found in the AI ecosystem is... shocking. The Numbers Don't Lie I ran pip-size on the most popular AI frameworks. Here are the results: Framework Package Size Total (with deps) torch 506.0 MB 2.5 GB 🤯 tensorflow 545.9 MB 611.9 MB paddlepaddle 185.8 MB 212.1 MB jax 3.0 MB 137.1 MB onnxruntime 16.4 MB 39.5 MB transformers 9.8 MB 38.4 MB keras 1.6 MB 29.5 MB The PyTorch Surprise Here's what happens when you pip install torch : torch==2.11.0 506.0 MB (total: 2.5 GB) ├── nvidia-cudnn-cu13==9.19.0.56 349.1 MB ├── nvidia

Why We Built 5 Products on FastAPI + Next.js (and Would Do It Again)
March 31, 2026 | 8 min read The Stack Decision That Shapes Everything Choosing a tech stack when you are a small team is one of those decisions that feels reversible but really is not. Sure, you can theoretically rewrite everything later. But in practice, whatever you pick on week one is what you are building on for the next two years. The frameworks you choose determine how fast you ship, how easy it is to hire (or onboard friends), and how much time you spend fighting your tools instead of building features. We are a group of friends from Tennessee building SaaS products under Obsidian Clad Labs. We have shipped five products on the same stack: FastAPI on the backend, Next.js on the frontend, PostgreSQL for the database. After a year of building, here is why we would make the same choice

The Complete DevSecOps Engineer Career Guide: From Pipeline Security to Platform Architect in 2026
The DevSecOps Engineer is one of the most in-demand roles in cybersecurity today. With a projected +36% market growth by 2032 and salaries ranging from $90K to $190K+ , this role sits at the intersection of software engineering, operations, and security. Unlike traditional security roles that gate-keep at the end of development, DevSecOps engineers shift security left -- embedding automated security checks, policy-as-code, and continuous compliance into every stage of the software delivery lifecycle. Whether you're a developer curious about security, a sysadmin moving into cloud-native, or a security analyst tired of finding bugs too late, this guide maps the complete career path from your first pipeline scan to designing enterprise-wide platform security. Start exploring the DevSecOps Eng
Knowledge Map
Connected Articles — Knowledge Graph
This article is connected to other articles through shared AI topics and tags.





Discussion
Sign in to join the discussion
No comments yet — be the first to share your thoughts!