pg83

5 ms·

31.
by pg83 2mo ago
For example, the itanium unwind ABI implementation lies between these three entities.
32.
by pg83 2mo ago
Tell me, are there any substantive comments on the text, on what has been done, and on the technical implementation, and not on the form?
33.
by pg83 2mo ago
How this differs (is better!) from prior art - https://github.com/pg83/solo#how-this-differs-from-prior-wor...
34.
by pg83 2mo ago
README.md was written by me, and I, of course, used claude/codex for it. In general, I do everything through claude/codex, the reasons are described in https://github.com/pg83/solo/blob/main/CON
35.
by pg83 2mo ago
Well, now it's possible! Furthermore, SoLo binaries can run, without modification, on glibc-based distros, alpine, and soon on android/bionic (not committed yet).
36.
by pg83 2mo ago
Glibc has a terrible history of binary incompatibility. If that's so hard to believe, try running binaries built on one distribution on other distributions. Linux has two stable ABIs: the kernel ABI for static programs, and, ironically
37.
by pg83 2mo ago
On the one hand, this is technically true, but on the other, what serious issues do you know that will cause problems in practice? I run tests on 1,000 of the most popular Debian packages.
38.
by pg83 2mo ago
Oh, cool, another prior art I didn't know :)
39.
by pg83 2mo ago
The binary itself is completely static; the link even provides commands on how to check this!
40.
by pg83 2mo ago
Isn't this a README? https://github.com/pg83/solo/blob/main/README.md
41.
by pg83 2mo ago
From a technical point of view, it is, of course, more important to me that my terminal widget (when it appears) can be used by anyone and in any way.
42.
by pg83 2mo ago
I don't like the GPL, and I don't like the GNU movement. In my opinion, they're hypocrites. Hypocrites steal the term "free" from the community when they're not, and, in fact, they're hypocritical when the
43.
by pg83 2mo ago
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.
44.
by pg83 2mo ago
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 compete. :)) I've updated the tables.
45.
by pg83 2mo ago
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!
46.
by pg83 2mo ago
I'll definitely do it as soon as the release happens!
47.
by pg83 2mo ago
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 least, I think so, and asan/ubsan agree with m
48.
by pg83 2mo ago
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?
49.
by pg83 2mo ago
At the very least, the ability to use the code as a library. A library under the GPL3 is unlikely to be popular.
50.
by pg83 2mo ago
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 becomes dual-licensed. At that point, I leave it as is and (ten
51.
by pg83 2mo ago
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 procedure described has been done many times,
52.
by pg83 2mo ago
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 speculation on the topic of LLM.
53.
by pg83 2mo ago
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 form, and that alone is quite valuable.
54.
by pg83 2mo ago
If we are talking about the process of direct code production according to a given specification, then 100%.
55.
by pg83 2mo ago
> 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.
56.
by pg83 2mo ago
> 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 mistakes and can miss something. > std::thread is m
57.
by pg83 2mo ago
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 tests - we also have regular fuzzing! - we even monitor cod
58.
by pg83 2mo ago
I don't know, I haven't measured it. For me, it's "instantaneous" enough that I don't have to think about it.
59.
by pg83 2mo ago
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 draw to the screen what has a
60.
by pg83 2mo ago
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!

More ›