I want more of this kind of comedy in my life. This article is hilarious.
Having worked at a company that built on top of WebRTC in 2015-2019, I directionally agree with the author. WebRTC is a pain in the ass, and a formidable piece of engineering at the same time. The problem it solves is too vast and ambitious. And it is not humans talking to AI models.
I use ebiten which through CGO uses glfw, so there’s a few layers of abstraction between Go and OpenGL. It’s true that I had to implement unicode rendering and a bunch of other things for either completeness or performance, but Ebiten was a solid foundation to build from.
If you're going to run a benchmark, at least post the results. I was planning on writing up a different blog post about the terminal optimization journey, but I actually used `kitten __benchmark__ --render` quite a lot to optimize it:
rune --version
Rune v1.2.1 (HEAD is 40bf9cc1)
Results:
Only ASCII chars : 1.13s @ 177.2 MB/s
Unicode chars : 1.44s @ 123.2 MB/s
CSI codes with few chars : 2.95s @ 33.9 MB/s
Long escape codes : 6.25s @ 125.5 MB/s
Images : 2.76s @ 193.1 MB/s
You just compiled 9 extensions, a purpose built benchmark program, a toy ssh shop I built, a toy TUI browser and Rune, in serial. It's right there in the output. Try `go build ./cmd/rune` for a fair comparison.
Having worked at a company that built on top of WebRTC in 2015-2019, I directionally agree with the author. WebRTC is a pain in the ass, and a formidable piece of engineering at the same time. The problem it solves is too vast and ambitious. And it is not humans talking to AI models.
reply