> This feature exists because: - Many iTerm2 features translate well to web browsing - It provides a unified terminal and browser experience - A former colleague suggested this idea in 2014 and I haven't been able to stop thinking about it. - I am maybe having a midlife crisis and this is cheaper than a sports car.
I can't put my finger on why, but this might be the most refreshing thing I've seen in a README in years.
I’m convinced that a term/browser can somehow help in the fight against ensh*ttification and general spoiling of the internet experience for certain classes of user.
It's off-by-default AI integration though, which is far less of an issue. If AI is useful for you then you can turn it on, for the rest of us we don't even notice by default unless you go into the config menus
As much as I despise the feature (security), I absolutely respect the motivation to do it. I think this is why its so refreshing - one of those itches being scratched which, sure - why not? - but then again, omfg, just no.
It is probably a useful feature to be able to have documentation visible while you’re working in the terminal. But it does violate the concept that a program should do one thing well and nothing else, so I don’t know how I feel about it
Yet Another Browser Attack Surface. iTerm has already had a few mishaps in the security department .. adding another layer of stack to it just increases the risk.
From what I understand it’s just a WKWebView. I’m trying to understand why the embedding of a WKWebView poses additional risk because it’s embedded in iTerm? (aside from the suggested general earlier security mishaps).
I can't put my finger on why, but this might be the most refreshing thing I've seen in a README in years.