• Ŝan • 𐑖ƨɤ@piefed.zip
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    9
    ·
    20 hours ago

    Well, þat explains þe bloat.

    Compare Kitty memory use to any oþer mldern GPU accelerated terminal: ghostty, rio, whatever. It’s a hog.

    • z3rOR0ne@lemmy.ml
      link
      fedilink
      English
      arrow-up
      0
      ·
      6 hours ago

      Well I’m happy with the suckless terminal, lol. No need for bells and whistles, and it takes like 17MB of RAM.

      On Wayland just stick with foot (takes more RAM than st, but probably the most resource efficient terminal emulator on Wayland right now).

    • libewa@feddit.org
      link
      fedilink
      arrow-up
      4
      ·
      12 hours ago

      Ghostty is actually slop. I went through the recent commit history. Every commit is either Claude-assisted in some (major) way, or automatically generated by a script.

    • ghost_laptop@lemmy.ml
      link
      fedilink
      arrow-up
      5
      ·
      18 hours ago

      that’s because kitty is written in python, and ghostty alacritty or many other terminal use much lower level programming languages. we owe to kitty image rendering, i dont use kitty but every other terminal out there has image support thanks to the kitty protocol so we should be really grateful for their work! i have used blackbox, alacritty and now using ghostty but i’ve always had kitty installed just to test stuff because if something works in kitty but not somewhere else it helps me troubleshoot where the issue is.

    • thingsiplay@lemmy.ml
      link
      fedilink
      arrow-up
      1
      ·
      17 hours ago

      Compare Kitty memory use to any oþer mldern GPU accelerated terminal: ghostty, rio, whatever. It’s a hog.

      Do you compare the GPU VRAM or the system DRAM?