[EPILEPSY WARNING] How fast should an unoptimized terminal run?
Channel:Molly Rocket · Length:51:03 · Published:2021-07-03 · Views:193863
Summary
Casey Muratori shows how fast a terminal renderer can run, building a simple reference renderer that handles Unicode and colored text far quicker than Windows Terminal. He argues that common excuses for slow terminals do not hold up.
Why HN recommends it
It is the canonical reference for the claim that modern software wastes hardware, and the proof-of-concept behind the Windows Terminal performance debate.
Casey spent <1 week making RefTerm, a skeleton proto-terminal with the same constraints Microsoft people had — HN, 2025
Software performance & optimization · Testing, debugging & developer tools
Subtitles (excerpt)
hello everyone and welcome to a little terminal rendering aside normally this is handmade hero but uh because last week and was a heatwave i had promised to do some terminal demo stuff and i did but it was silent and in the middle of the night and only about five or ten minutes or something uh so i'm gonna do the actual terminal demonstration with talking uh today and uh just to give people some background about this there was for reasons that are totally not worth going into a lot of the standard sort of nonsense developer excuse factory stuff going on with regards to mono space text rendering and uh generally speaking one of the problems that we have that's endemic in development today is that instead of people just acknowledging the fact that pretty much 100 of software is like either 100 or 1 000 times slower than it should be uh they just make all these excuses as to why that is correct um there are so many that i don't even know what they all are off the top of my head but you know they range anywhere from ones that are actually they're not they're not excuses they're they're potentially even reasonable explanations like you know we don't care about that we just want fast time to market
On Hacker News
Worth watching Casey Muratori's series of videos on terminals, and how to implement them, where he often makes specific comparison to Windows Terminal. He has some specific criticisms that are easy to disagree with, but the vast majority are well warranted. His broader series of videos on the topic are even worthwhile from a purely "software engineering education" standpoint. [VIDEO] I feel a bit… — dundarious, 2022-05
As luck would have it, here's the continuation to Windows Terminal. Casey Muratori made a reference terminal renderer: [LINK] This uses all the constraints that the Windows terminal team cited as excuses: it uses Windows subsystems etc. One person, 3k lines of code, it runs 100x the speed of Windows terminal. See the epic demo (and stay till the end for color output): [VIDEO] — dmitriid, 2021-07
It's well known, but this video[1] is a proof of concept demonstration from 4 years ago, Casey Muratori called out Microsoft's new Windows Terminal for slow performance and people argued that it wasn't possible, practical, or maintainable to make a faster terminal and that his claims of "thousands of frames per second" were hyperbolic, and one person said it would be a "PHD level research project… — jodrellblank, 2025-07
Casey Muratori has some great YouTube videos (a.k.a.: rants) about the end-user visible performance degradation over the last two decades despite computers becoming 10-100x faster by various metrics. E.g.: Visual Studio Rant [LINK] How fast should an unoptimized terminal run? [VIDEO] The root cause is that Microsoft simply doesn't have performance as a priority. It's not a KPI for (almost) anyone… — jiggawatts, 2024-05
Author here. It is very implausible :) After watching an inspiring video on terminal optimization [1], I started doing some napkin math on how fast my ex-employers' programs "should" run and how many resources they "should" take up. With my very small sample size (N=5), those numbers definitely hold. My big untested assumption is that most startups have even worse codebases than what I've experie… — surprisetalk, 2023-11
Related videos
- Refterm Lecture Part 1 - Philosophies of Optimization · Molly Rocket · 18:41
- The Only Unbreakable Law · Molly Rocket · 53:25
- Why the Dutch Wait Less at Traffic Lights · Not Just Bikes · 10:34
- Joe Armstrong & Jeremy Ruston - Intertwingling the Tiddlywiki with Erlang | Code Mesh LDN 18 · Code Sync · 44:38
- Arcologies · Isaac Arthur · 28:43
- The paradox of choice | Barry Schwartz | TED · TED · 20:23
- DjangoCon 2008 Keynote: Cal Henderson · Google for Developers · 1:02:43
- The Most IMPORTANT Video You'll Ever See (part 1 of 8) · wonderingmind42 · 9:17
- Self-filling water bottle: BUSTED! · Thunderf00t · 16:52
- Why Grocery Shopping is Better in Amsterdam · Not Just Bikes · 3:46
- The surprising science of happiness | Dan Gilbert · TED · 21:20
- Life is easy. Why do we make it so hard? | Jon Jandai | TEDxDoiSuthep · TEDx Talks · 15:10
- The Dutch Solution for Safer Sidewalks - Continuous Sidewalks · Not Just Bikes · 3:44
- Colonizing Mars · Isaac Arthur · 34:32
- The Most Powerful Computers You've Never Heard Of · Veritasium · 20:12
- a better way to count · jan Misali · 18:01
- Tiffany: The Name That Cheats Death · CGP Grey · 8:56
- I'll Let Myself In: Tactics of Physical Pen Testers · Wild West Hackin' Fest · 44:55
- America Always Gets This Wrong (when building transit) · Not Just Bikes · 15:27
- Why Western Designs Fail in Developing Countries · Design Theory · 27:36