> Also funny/sad: both call themselves 'cross-platform', but then don't support Windows (only various UNIX variants).
replyThis still qualifies as cross-platform though. Cross-platform doesn't mean "all the platforms" or "all the platforms with the biggest market share in the segment of the application".
Maybe, but it reminds me of the bad old days when Microsoft called their applications 'cross-platform', and then they just meant different flavours of Windows ;)
replyI mean, I share the sentiment, and IMO they should support at least the BSDs (there are official FreeBSD ports for both Kitty and Ghostty but no mentions of them in both websites)
reply> Also funny/sad: both call themselves 'cross-platform', but then don't support Windows
replyBoth might have thought 'If you are patient enough to tolerate a slower web based start menu, you are probably not a target market for a hardware accelerated terminal' :D
Proper Windows support is not easy to archive. Plus with Windows Terminal being good enough and open-source, there isn't much incentive to support it.
replyWindows Terminal doesn't support Kitty Graphics Protocol (yet?: https://github.com/microsoft/terminal/issues/8389).
replyThat's the one thing I always check first in a terminal because I have this pet project to run emulators in a terminal ;)
https://github.com/floooh/chipz-kitty
(works fine in Kitty and Ghostty, wezterm theoretically also supports the Kitty protocol but at some point just freezes)
Honestly, as fun as it is using KGP, I don't consider it critical for any real use cases.
replyIf you need a GUI, just use a GUI.