Earlier quoted context omitted.
[flagged]
> to refute yours Oh boy, you still don’t get it! The fact you saw it as something that needed refuting really says a lot more about you than anything else. It’s actually ok to let positive comments about other terminals go unrefuted and just get on with your life ;) But seemingly you can’t let it go. By the way, nobody is choosing ghostty over kitty just because of the release notes for 1.0.1, so no need to fret! If…
Déjà vu: Ghostly CVEs in my terminal title
41–50 of 68 posts
Re: Déjà vu: Ghostly CVEs in my terminal title
#42Earlier quoted context omitted.
It’s interesting how singularly passionate you are about Kitty, with almost all of your comments for the last year (or longer) being about Kitty. Don’t you have something more interesting to do with your time than to find opportunities to say: nah Kitty is better ;) I was just finding something to be impressed about, considering it has only just gone public and open source (as opposed to a mature project with establi…
FYI: aumerle is kitty's maintainer. i don't know why he is talking about the project as if unaffiliated.
Re: Déjà vu: Ghostly CVEs in my terminal title
#43Re: Déjà vu: Ghostly CVEs in my terminal title
#44Earlier quoted context omitted.
> to refute yours Oh boy, you still don’t get it! The fact you saw it as something that needed refuting really says a lot more about you than anything else. It’s actually ok to let positive comments about other terminals go unrefuted and just get on with your life ;) But seemingly you can’t let it go. By the way, nobody is choosing ghostty over kitty just because of the release notes for 1.0.1, so no need to fret! If…
[flagged]
It’s actually incredible you still don’t see. It’s impossible for my comment to be wrong, because I get to decide what I’m impressed by. Just because you wrote a terminal, doesn’t mean you suddenly have authority to tell others what they should or shouldn’t be impressed by. You have no such authority :) If I’d claimed that ghostty’s release velocity is better than kitty’s (or vice versa), then you’d have a point. But I didn’t ;)
> You have provided increasingly desperate personal attacks.
Actually, I haven’t. I also don’t have skin in the game and have no reason to be desperate. I haven’t devoted a significant amount of my time to writing a terminal, for example. And I don’t even use ghostty (yet).
Downvotes on your comments are still ticking up, as are upvotes on mine. I know it’s not kosher to talk about votes, but I don’t know what other signal you need to maybe take a break for a bit and calm down :)
Re: Déjà vu: Ghostly CVEs in my terminal title
#45I really wish that 1% of the sustained effort that is currently being devoted to building terminal emulators and TUI applications was collectively redirected at researching a better future to fill this niche. Terminal emulators and TUI applications belong with the DMG Gameboys, Commodore 64's, and DOSBoxes: as a historical curiosity and something for the enthusiasts to enjoy after hours. But we've come to rely on the…
The current effort can at least be pointed towards something.
Re: Déjà vu: Ghostly CVEs in my terminal title
#46I really wish that 1% of the sustained effort that is currently being devoted to building terminal emulators and TUI applications was collectively redirected at researching a better future to fill this niche. Terminal emulators and TUI applications belong with the DMG Gameboys, Commodore 64's, and DOSBoxes: as a historical curiosity and something for the enthusiasts to enjoy after hours. But we've come to rely on the…
It's X11/systemd/ipv4 problem. People agreeing there is a problem doesn't mean that any single solution will be accepted. With terminals you have a system that works with anything from HPC-s to serial devices. An alternative would probably need to drop support for something, meaning congratulations: The number of standards increased by 1 - probably 2 by the time that people unsupported by the modern alternative decid…
Re: Déjà vu: Ghostly CVEs in my terminal title
#47Earlier quoted context omitted.
[flagged]
> Still waiting for you to admit you were wrong in the first place. It’s actually incredible you still don’t see. It’s impossible for my comment to be wrong, because I get to decide what I’m impressed by. Just because you wrote a terminal, doesn’t mean you suddenly have authority to tell others what they should or shouldn’t be impressed by. You have no such authority :) If I’d claimed that ghostty’s release velocity…
Re: Déjà vu: Ghostly CVEs in my terminal title
#48Earlier quoted context omitted.
I believe it could. A shell could reduce capability by default for all executed shell scripts (file or inline on the prompt) and require opt in to not do this. Something akin to a umask of sorts. It’d break exceedingly few real scripts. (Hand waving a lot here with the “opt in” mechanism to avoid that being scripted but I have ideas) Also note my thoughts (very much not even close to being a proposal) are very raw. I…
So if I am to understand your proposal more concretely it is something like implement an escape code that the shell can use to turn off all other escape codes (presumably with some kind of listing mechanism) and then have the shell do that before launching any third party script/program/function? How would the shell know which escape codes the program it is running needs? I can, kind of, see the utility of a pledge()…
1. The shell could have a keybind (say, ctrl+enter) which runs the command with (for example) only styling enabled (CSI m sequences).
2. You could write a wrapper around any program to do the same. The shell doesn't need to know anything about the system, but instead you have a wrapper that disables and then reenables said sequences.
3. A program itself can opt in by turning on the feature at launch. This allows CLI / TUI developers to "safeguard" their programs from malicious attacks.
Re: Déjà vu: Ghostly CVEs in my terminal title
#49I really wish that 1% of the sustained effort that is currently being devoted to building terminal emulators and TUI applications was collectively redirected at researching a better future to fill this niche. Terminal emulators and TUI applications belong with the DMG Gameboys, Commodore 64's, and DOSBoxes: as a historical curiosity and something for the enthusiasts to enjoy after hours. But we've come to rely on the…
Re: Déjà vu: Ghostly CVEs in my terminal title
#50Earlier quoted context omitted.
> Still waiting for you to admit you were wrong in the first place. It’s actually incredible you still don’t see. It’s impossible for my comment to be wrong, because I get to decide what I’m impressed by. Just because you wrote a terminal, doesn’t mean you suddenly have authority to tell others what they should or shouldn’t be impressed by. You have no such authority :) If I’d claimed that ghostty’s release velocity…
[flagged]
Actually, it doesn’t, as it’s very clear you still don’t understand what I’m saying XD
If I was comparing ghostty to kitty, I can obviously be wrong. But I was just saying I’m impressed, which literally can’t be wrong unless I’m lying about being impressed.
It’s like if I look across a lake and say “what a lovely view”. And someone comes by and says “no there’s a much better one where I was standing, you should take back what you said or provide evidence to your claim”. Don’t you see how silly this is ;)
> Do you actually believe ghostty has a development velocity faster than its peers, specifically, kitty and WezTerm? Yes or no.
You said you didn’t give a “rat’s ass” about my opinion ;)
This is where you’ve gone wrong. It don’t know or care whether ghostty has a development velocity faster than kitty. I didn’t say it did. Nobody in this sub-thread has said anything (good or bad) about kitty. The only person interested in ghostty vs kitty in this sub-thread is you.
So the question you’re demanding that I answer is like demanding I prove that the view I was impressed with across the lake is better than the view you had. When it really doesn’t matter which view was better. It’s possible to be impressed by something in isolation, without it being turned into a competition.
I’m not answering your question because I have no part to play in the 1-person argument you’re having with yourself about whose development velocity is faster, when nobody was making the comparison to begin with (except you).
I feel like I’m wasting my breath though, but at least I can say I tried! And I suspect HN comment depth limits may kick in soon. So I’ll bow out now and give you the pleasure of the last word, since you certainly seem to need it more than me ;)