• Markaos@lemmy.one
      0·
      13 days ago

      As @Treeniks@lemmy.ml pointed out, the author considers something as small as spawning a separate process for each window to mean a “non-native experience” (wait till they see how web browsers work)

    • Treeniks@lemmy.ml
      0·
      13 days ago

      They explain it a bit here: https://mitchellh.com/writing/ghostty-and-useful-zig-patterns

      Also, calling out the warning signs, my bar for a native platform experience is that the app feels and acts like a purpose-built native app. I don’t think this bar is unreasonable. For example, I don’t think it’s unreasonable to say that Alacritty is kind of not native because new windows create new processes. Or that Kitty is kind of not native because tabs use a non-native widget. And so on (there are many more examples for each).

      So nothing wrong with Kitty on MacOS e.g., but the “feel” is not native. Personally don’t care too much about that, but the author seems to do.

      • SuperFola@programming.devEnglish
        0·
        13 days ago

        This smells like bullshit because it’s just based on things users do not see (processes) or do not care about (the style used for your tabs).

        • Treeniks@lemmy.ml
          0·
          13 days ago

          Yeah I agree the table is very odd, but the project looks awesome anyway. Some users may care about things using native widgets when it comes to theming and stuff, though I wouldn’t even know what I’d call “native” on Linux. Is GTK native? Qt?

      • SuperFola@programming.devEnglish
        0·
        13 days ago

        Kitty is mentioned once in the article and that’s it. Doesn’t even mention its downside and how ghostty is so much better according to them.

        It’s a great project and all, but I’d love if people could stop stomping on others work just to appear better.

    • petey@aussie.zone
      0·
      13 days ago

      Yeah, I’d say Kitty and Alacritty work pretty well on Linux. Makes this comparison table seem like bs

  • lemmeBe@sh.itjust.works
    0·
    13 days ago

    Just had a look at Kitty and from what I understand, it’s an emulator, and it’s fast, has ligatures.

    Since I rarely use terminal outside of VS Code, i.e. zsh shell on Mac, I don’t quite understand what would I get from it?

    Reviews say it’s fast, has low latency between typing and the text appearing on the screen - I’m not seeing latency either way. The text is there, can it get any faster? 😅

  • ericjmorey@programming.dev
    0·
    13 days ago

    I think that Hashimoto is using this project to iron out details that are left unaddressed due to convenience for other projects and the very low impact of any single issue Hashimoto has addressed. But much like with Apple projects, Hashimoto intends for the the end product to have greater value than the sum of the parts. Unlike Apple, it will be perfomant cross platform.

    I think the only way to evaluate a project like this is to ignore the feature comparison charts and use it to see if it really is better when those details are addressed. I have a feeling that many people will agree and most will shrug their shoulders and not give it a second look if they even gave it a first one.

    I’ll be trying Ghostty out soon. I hope it’s great. But I’m not expecting to be blown away.

  • key@lemmy.keychat.orgEnglish
    0·
    13 days ago

    Seems the pitch is just that it supports Apple specific bells and whistles like the emoji bar and beyond that has the stuff other terminals have. I use tilda and use that because it has a critical core feature I haven’t seen in other terminals: it appears full screen over all other windows with a keypress and disappears the same way. Since I use terminal heavily I don’t want to treat it as just another window but as a first class experience which tilda allows. I don’t really get why you’d make yet another terminal without some fundamental core functionality difference like that.