Viewing profile — pg83

sixel is implemented, as is the kitty keyboard protocol, but there are no plans for the kitty graphics protocol, and most likely there won't be one.

We're currently tied in wall (yours is better at ASCII, while random is worse). But considering that user is better for me in both cases (algorithmic), we'll still have a chance to…

I'd try the master, but I have no experience with the zig ecosystem. I'd end up compiling something wrong and getting weird results. I'd rather wait for the official binaries!

I'll definitely do it as soon as the release happens!

Yes, "blazingly fast", but not in Rust! In fact, I have my own development model in C++, which allows me to write at approximately the same level of safety that Rust provides (at l…

There are no plans for this right now. I don't use graphics in the terminal myself, but if there's a need, why not?

At the very least, the ability to use the code as a library. A library under the GPL3 is unlikely to be popular.

The procedure is quite simple in principle: each new contributor confirms their permission to use their code under two licenses—MIT and GPL3. After a while, the entire codebase bec…

I'll probably stick to the perspective expressed to me by the lawyer (I actually consulted on this topic), rather than the opinion of some random "GPL zealot" on the internet. The …

Expert opinion versus expert opinion. I will probably stick to my point of view and suggest that you either offer a benchmark or show a specific problem in my code, without specula…

I'm glad someone noticed this, but ragel is a very niche tool; few people have heard of it! I believe my parser is the first complete description of a terminal output parser in FSM…

If we are talking about the process of direct code production according to a given specification, then 100%.

> The moronic naming immediately undermines that claim. It's quite obvious to me that professionalism in product manufacturing correlates very weakly with naming :) Proof me wrong.…

> What do you mean you didn't notice? I saw another comment about Claude below, are you not even reviewing the output? Of course I looked at the LLM output, but people, uh, make mi…

I assure you, this is a very professionally made product: - we have 5,000 tests covering all aspects of terminal behavior - we have address sanitizer and ub sanitizer runs of these…

I don't know, I haven't measured it. For me, it's "instantaneous" enough that I don't have to think about it.

It's VERY difficult to measure. But I can say that shitty has the best damage tracking model among foot/kitty/alacritty/ghostty. It's best in the sense that it's cell-exact; I only…

I guess I just didn't notice. In any case, it wouldn't have been std::thread, but https://github.com/pg83/std/blob/master/std/thr/thread.h from my bike lib!

Speed itself may not be very important, but it is a very interesting challenge in itself - to prove to yourself that you can surpass the state of the art!

I'm a huge proponent of AI, as long as there's a human in the loop and strong models are used. In fact, it's even reflected in our CONTRIBUTING.md that we prefer LLM-assisted code!…

I hoped that at least someone would like it :))

I'm not imposing my opinion, but in my experience, iterm2 is the slowest terminal emulator I know of, so I didn't even bother trying. But overall, I'll add iterm2 to the list, too.…

It's not that it's a serious problem, it's just that for me, as a perfectionist, flicker is very noticeable when resizing.

No, there are no such plans right now, but overall, the project's architecture allows for easy separation of different layers for developing a terminal emulator - the parser, in th…

For example, flicker free resizes for MacOS, something that neither Kitty, nor Alacritti, nor Ghostty can boast of.