HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
cmuratori
refterm
HISTORICAL RECORD2021–2026
cmuratori / refterm · Not publicly available

refterm

Discover this repository through its Hacker News conversations.

25Distinct people
32Mentions
0Explicit recommenders
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A public description has not been verified.

Where it is used

The source check is incomplete. Verified examples will appear here.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 1:56:48 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year32 dated mentions

Observed mentions: 2021-07-03 22:39:42 UTC to 2026-07-19 20:27:01 UTC.

051015202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 18 mentions; 3 submissions, 15 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 8 mentions; 0 submissions, 8 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC18315
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC808
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC202
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC000
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC303
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC101

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
refterm v2 refterm is a reference renderer for monospace terminal displays. It was designed to demonstrate that even in the worst-case scenario - extremely slow Unicode parsing with Uniscribe and extremely slow glyph generation with DirectWrite - it is still straightforward to achieve reasonable frame rates and reasonable throughput by being sensible. Please note that refterm is UTF-8. If you are doing tests with it, you must use UTF-8 encoded files or command output. Simple Code, Reasonable Speed refterm actually isn't very fast. Despite being several orders of magnitude faster than Windows Terminal, refterm is largely unoptimized and is much slower than it could be. It is nothing more than a straightforward implementation of a tile renderer, with a very simple cache to ensure that glyph generation only gets called when new glyphs are seen. It is all very, very simple. A more complex codebase that parsed Unicode and rendered glyphs itself would likely be much faster than refterm for many important metrics. VT code and line break parsing in refterm has had one piece of optimization in v2. It now checks each 16-byte block for control codes before actually running the parser. This was done to help test high-bandwidth throughput. The actual control code parser has still not been optimized at all, however. TL;DR: refterm should be thought of as establishing a modern minimum speed at which a reasonable terminal should be expected to perform. It should not be thought of as a maximum to aspire to. If your terminal runs slower than refterm, that is not a good sign. Feature Support refterm is designed to support several features, just to ensure that no shortcuts have been taken in the design of the renderer. As such, refterm supports: Multicolor fonts All of Unicode, including combining characters and right-to-left text like Arabic Glyphs that can take up several cells Line wrapping Reflowing line wrapping on terminal resize Large scrollback buffer VT codes for setting colors and cursor positions, as well as strikethrough, underline, blink, reverse video, etc. These features are not designed to be comprehensive, since this is only meant to be a reference renderer, not a complete terminal. Code Layout The important code for the reference renderer resides in three simple files: refterm.hlsl - shader for doing tile-based rendering refterm_glyph_cache.h/c - cache for mapping Unicode runs to glyphs The rest of the code - refterm_example_*.h/c - is just there to verify that the API for the glyph cache conveniently supports all the features a terminal needs. The code in those files may be useful as a vague reference, but no thought was put into their design so it is not likely to be directly useful. Fast Pipes Prior to v2, it was assumed that conhost had to be bypassed in order to do high-throughput terminal processing. However, after some testing it was determined that so long as conhost receives large writes, it is actually within 10% of the fast pipe alternative. So it appears that so long as you either directly call WriteFile with large buffers, or you use stdio with large buffers and set stdout to binary mode, you can get reasonable speed going through conhost!
Read the full README on GitHub

What Hacker News says

18 sources
For a basic example of why you would want GPU acceleration, have a look at refterm: https://github.com/cmuratori/refterm Even processes that you wouldn't think would be impacted by a terminal can be hurt relaly bad by your terminal's performance: your compiler's logs, etc. The GPU rendering part merely guarantees that your terminal sticks at 60FPS (or, whatever your refresh rate is) if the processing behind is efficient.
In WezTerm – A GPU-accelerated cross-platform terminal emulator and multiplexer
It's here: https://github.com/cmuratori/refterm That issue was closed but the current open issue which acknowledges this is a real problem is here: https://github.com/microsoft/terminal/issues/10462 Here is a comment on the code directly from a contributor at Microsoft: > @AnuthaDev We‘re quite aware about the code and are extremely happy about what was created there. I mean it seriously: It sets a great goal for us to strive for. Unfortunately the code is intentionally GPLv2 licensed and we‘ll honor this wish entirely. As such no one at Microsoft will ever look at either of the links. > I‘m the person who‘s tasked with building an equivalent solution and you may subscribe to #10461 to get updates of my progress. Unfortunately our existing project isn’t straight forward to modify the same way we could build a terminal from scratch. A lot
Read the rest
of parts of this project must be rewritten and as such it‘ll take a bit for us to catch up. But we will - it’s only a matter of time. https://github.com/microsoft/terminal/issues/10462#issuecomm...
In It takes a PhD to develop that
> might not be fully applicable to the development of mainstream commercial software that has to try to be all things to all people, including considerations like internationalization, accessibility, and backward compatibility. Windows Terminal has none of that. And his refterm already has more features implemented correctly (such as proper handling of Arabic etc.) than Windows Terminal. See feature support: https://github.com/cmuratori/refterm#feature-support Also see FAQ: https://github.com/cmuratori/refterm/blob/main/faq.md
In It takes a PhD to develop that
Reading the thread itself, it’s a bit of both. Windows Terminal is complex, ClearType is complex and Unicode rendering is complex. That said… https://github.com/cmuratori/refterm does exist, does not support ClearType, but does claim to fully support Unicode. Unfortunately, Microsoft can’t use the code because (a) it’s GPLv2 and (b) it sounds like the Windows Terminal project is indeed a bit more complicated than can be hacked on over a weekend and would need extensive refactoring to support the approach. So it sounds a bit more like a brownfield problem than simply ignoring half the things it needs to do, though it probably does that too.
In It takes a PhD to develop that
This particular case was discussed at length on Reddit and on YC News. The general consensus was that the Microsoft developers simply didn't have performance in the vocabulary, and couldn't fathom it being a solvable problem despite having a trivial scenario on their hands with no complexity to it at all. The "complaining developer" produced a proof of concept in just two weekends that notably had more features[1] and was more correct than the Windows Terminal! RefTerm 2 vs Windows Terminal in action: https://www.youtube.com/watch?v=99dKzubvpKE Refterm 2 source: https://github.com/cmuratori/refterm One of the previous discussions: https://news.ycombinator.com/item?id=27775268 [1] Features relevant to the debate at any rate, which was that it is possible to write a high-performance terminal renderer that also correctly renders Unicode. He
Read the rest
didn't implement a lot of non-rendering features, but those are beside the point.
In It takes a PhD to develop that
> Am I the only one who really enjoys Windows 11 so far? Probably not, but consider that people have a lot of different use cases for their computer and a lot of different priorities and Microsoft has been pretty consistent lately about ignoring pretty much any of them that aren't "I really wish my desktop were a clunky tablet". > I really like the new UI which feels more modern and harmonic Subjective, but feeling more modern is precisely the opposite of what I want in a UI. Modern means slow and cumbersome with lots of wasted space, sparse options, and unreadable widgets. > Control Panel is still in there somewhere but why should I care? Control Panel had nothing wrong with it and probably still has settings options that are missing from the new ones? > new GPU accelerated Terminal is really nice It's performance is remarkably terrible
Read the rest
for something that's GPU accelerated. Casey Muratori has said a lot about it. https://github.com/cmuratori/termbench and https://github.com/cmuratori/refterm were a result. It doesn't mean a lot in terms of quality of Windows 11, I just think it is a good illustration of modern Windows team's development practices. > Does it have tons of telemetry, cruft from 20 years in the kernel and some rough edges? Cruft is fine because it is there for backwards compat, which is huge for a tone of desktop use cases. Linux Kernel has a ton of cruft too for the same reason. Telemetry is bullshit and wastes my computer's resources to effectively spy on me. > Is the hardware requirements a bit ridiculous? The hardware requirements are very ridiculous. Windows 11 is not revolutionary, but somehow manages to require twice the minimum specs of ten in some metrics, and a TPM module. > To each their own I guess but it sometimes feels a bit depressing how HN crowd trashes every OS. They all have problems, big problems, so they all deserve it. I find it more remarkable that people consistently try to say that everything is actually ok! > Is everyone here still using C64, Windows 2000 or OS9 because it „was the last good system“? God I wish they were still viable.
In Windows 11 available on October 5
> I don't get it either - I use Windows (the default cmd, Powershell and Cmder), Linux and MacOS and don't recall a terminal emulator being slow... ever. You might be a particular type of person... I don't remember Windows Cmd being not slow, ever. It feels extremely sluggish. It supposedly has something to do with Windows ConHost, but I don't know about the details. In fact, even most terminals on Linux are unbearable to me. Not only do the antialised vector fonts tire the eyes on sub-4K screens - most of the terminals I've tried feel slow as well, though not as slow as Windows Cmd. http://danluu.com/term-latency/ https://github.com/cmuratori/refterm Personally I use xterm with bitmap fonts whenever I can, it feels sooo good. It has both crisp font rendering as well as being reasonably fast/responsive. (It's probably not the fastest ever
Read the rest
in throughput if you want to display /dev/urandom, but that's not my benchmark).
In Warp: Fast, Rust-based terminal (waiting list)

Showing the 15 most recent of 18 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.