Not at all, it just had a release a few months ago,

GNU Screen v.5.0.0 is released posted by anaumov, Wed 28 Aug 2024 09:41:30 PM UTC

So moving to a newer / less "bloated" terminal may also just wind the clock back and cause you to encounter a similar sequence of vulns again, like some kind of unfortunate real-world "New Game Plus".

What others am I missing?

It pains me to think people are still exposing themselves to this class of risk because of whatever iTerm2's latest and greatest idea is.

I use iTerm2, mostly because that's what I'm used to: I installed it on my first Mac years ago when Terminal.app was really bad. I'm willing to switch to another terminal, but I don't see yet how iTerm2 is so much worse than the competition security-wise.

(I also don't understand the general animosity towards an opensource project with one developer doing all the work for 15 years.)

Here’s another: https://www.bleepingcomputer.com/news/security/iterm2-patche...

And another: https://www.cvedetails.com/cve/CVE-2019-19022/

Point being: it’s not hard to see what I’m talking about if you look up previous vulnerabilities in iTerm2, particularly around its sophisticated integration features. (I suppose I talk about this enough that it might be worth compiling all the history I’m aware of somewhere, I don’t want to sound like I’m just making this up)

It’s also notable that iTerm was found vulnerable to the same bug discovered recently in Ghostty: https://threatintelligencelab.com/blog/cve-2024-38396-a-crit...

> I also don't understand the general animosity towards an opensource project with one developer doing all the work for 15 years

I have nothing against George Nachman and iTerm2 is certainly an achievement, one that I probably couldn’t replicate myself. Nonetheless I feel the need to hold my terminal emulator to higher standards because it processes sensitive data and untrusted input with (inherently) poor isolation between the two. Until Ghostty I used Terminal.app for many years, having previously switched away from iTerm2 after the vulnerability discovered in 2017. That’s still what I recommend to people because it has a much smaller feature set and thus attack surface compared to iTerm.

Following this discussion I decided to give Ghostty and kitty a try. I kept Ghostty, mainly because the shortcuts I use the most in iTerm2 are there and I like the default theme (yes, I'm a simple person.) It has less features / integrations I don´t use anyway so I guess the attack surface is smaller.

I don't think there are larger lessons to draw from that occurrence. A reputation for security has to be earned, and Ghostty hasn't been around long enough for that. From my vantage point it's on track, but only time will tell.

The others do sound useful too -- I personally hit a lot of spurious "tab output indicator" notifications in iTerm2, but if it _did_ work I could see how giving it up would be painful.

I’ll give it another go at the weekend.

https://ghostty.org/docs/config/reference#window-colorspace

Here's the relevant docs page, which I hope explains why I mistakenly thought that transferring a theme directly from iTerm to Ghostty was possible. You could upload your theme to the website they're being sourced from, and wait a week. But that's clearly not the same thing.

https://ghostty.org/docs/features/theme

I configured

    bold-is-bright = true

https://ghostty.org/docs/config/reference#bold-is-bright

It is? Because as far as I can tell it is deliberately quite different from iTerm2. No GUI for preferences, for instance.

Not knocking it, it's a great terminal. I wouldn't describe it as "familiar" though, unless you're switching from, say, WezTerm or Alacritty.

I don’t personally iTerm2 to be be either of those.

(I can't remember why I switched. It must have been 10 years ago now, maybe more, and I've stuck with iTerm2 ever since (even though it annoys me with a new beta update practically every time I launch it). It could have been nothing fancier than the vertical window split. But there was definitely something that persuaded me to change!)

EDIT: this did get me wondering, and I noticed two things it does have that it looks like Terminal still doesn't: configurable mouse selection word boundary chars, and implicit copy-to-clipboard on selection. As an inveterate mouse selector, I wonder if it was these. I might well actually have the word boundary chars still set to the default ("/-+\~_." is what I've got), but I do use the click-to-copy a lot.

Why don't you just use the stable releases?

I used Terminal for many years, too, but switched to iTerm2 a little over a year ago as I wanted to learn neovim.

- split pane support - profile switching (I have my colors change for different environments I ssh into). - tmux integration

It also has every feature known to exist in this space.

I agree though that the world is moving in the way of tmux - I'll get around to switching occasionally.

> GNU Screen seems to be stagnant

Is it stagnant or mostly complete?

Nothing, it works great. As someone who tried a bunch of alternatives: sorry but it's a waste of time unless you look at the long list of iterm2 features (terminal.app has many of them anyway) and think you might use those often (I don't, quite happy with my other apps covering for most of the features missing from the terminal.app): https://iterm2.com/features.html

Long live Terminal.app

  v4 2006: feature complete, survived 18 years of attacks
  v5 2024: new auth functionality, survived 4 months of attacks

You can do some complex stuff with them, but I "just" use them to highlight specific things when tailing output. Some of it might be possible with grep, but probably not

That's not a new thing...

I get old code smell, and why folks might want something architecturally different, whatever - but screen is functionally feature complete.