Kemdirịm

Sitting in chairs, pontificating and doing objectively cool shit. prev @messagebird, @openpurpose, @lace_io

[Kemdirịm @Kemdirim]

Pray at the altar of hard work.

[Egor @egorvert]

This is a loader animation I made for an internal tool of which I am the sole user.

It took millions of tokens and multiple minutes of iteration (it was two prompts).

[Mitchell Hashimoto @mitchellh]

I like to look at claims like this in case I can improve Ghostty. I grabbed your source and immediately spotted the issue: your read loop overwrites a 64 KiB ring. Everything older is discarded unparsed per tick. You're faster because you're not actually terminal emulating.

It means the number isn't a throughput number. In a kitten benchmark run at the rate you're claiming, roughly 6.6 MB arrives per 60 Hz tick and 64 KiB of it gets parsed. You're read(2)-ing 100% of the data and parsing about 1% of it.

There are other minor issues (a small fixed scrollback in a preallocated ring buffer, no grapheme clustering, throwing away data like OSC 8 URIs, etc.), but the major one is simply that you're discarding ~99% of the input.

For plain text, e.g. your cat benchmark, the final screen ends up looking right, but the scrollback is missing 99% of the file and each retained chunk starts mid-line. As soon as there are escape sequences in the dropped spans, your emulator is fully out of sync and invalid: a cut inside a CSI prints the parameters as text, and any SGR, mode, title, or alt-screen change in the gap is just... gone.

FYI, this is why I don't like when people point at refterm as a terminal benchmark. refterm implements a TINY subset of what a terminal emulator must support, it's closer to a fast file reader, not a terminal emulator.

I also don't mean any shade by this. I like to look at technology objectively to try to learn something and improve my own craft and work. So I'm sharing what I found.

I modified your code very slightly to parse on every full buffer (rather than per tick). And the results are attached. Both use main commit in each repo at the time of this post.

Note the graph is in log scale, the discrepancy between performance for things like Kitty images is measured in GB/s.

[Adam Whitcroft @AdamWhitcroft]

6/8 things here are mine. Nothing beats personal software.

[Niko @nikolasklein]

5.5 years of url hoarding gives you this

[Frank Bach @zendadddy]

@digitalshane_ vibes

[Butterfly @bflycomputer]

Pond, our linux operating system, is now available for anyone to try!

Our updated website includes the installers and a detailed look at the operating system

https://t.co/PXszgKgdzK

[Eureka @eureka_seamless]

Introducing Eureka Studios. 🚀
https://t.co/Icrv6aRTDA

We make games that feel like home: our roads, our jokes, our people.

Danfo Run was the first.
@eurekastudioshq

[Kemdirịm @Kemdirim]

Played the worst game of football today. My legs gave out mid game lmaooo.

Dreadful performance, definitely training with the reserves for the foreseeable future. 🫠

[Kemdirịm @Kemdirim]

Skip skip skip. 🙏🏿

[azeez @iam_azeezadio]

@Kemdirim let’s do one more infrared mat sculpt.

[owen cyclops @owenbroadcast]

yeah i have a gambling addiction. i can’t stop betting on myself

[Jakub Krehel @jakubkrehel]

Added a new skill: /teardown

It creates a technical illustration of any object and lets you customize individual parts, colors and annotations. You can then export the result as an SVG or PNG.

npx skills add jakubkrehel/skills

[Frank Bach @zendadddy]

I’m not afraid to die and that brings so much relief

[Thariq @trq212]

@lydiahallie wait is it just me or is Opus 5.5 dumber

[Kemdirịm @Kemdirim]

@Deshdnl This is facts. 😂

[Ade @Deshdnl]

"Brothers with a common debt" ❤️

[Kemdirịm @Kemdirim]

@Jessica_Egbedi @iam_azeezadio 🫶🏾🫶🏾

[Kemdirịm @Kemdirim]

Blessed with good company.

[Kemdirịm @Kemdirim]

@AfredFoster @iam_azeezadio Thank you!

[Kemdirịm @Kemdirim]

@PerfectAnyanwu @iam_azeezadio 🙏🏿🙏🏿

[Kemdirịm @Kemdirim]

@thatdarkboyy @iam_azeezadio Thank you!

[Kemdirịm @Kemdirim]

@NifemiOlojo @iam_azeezadio Lool