I was excited to learn about two new terminal emulator app which seemed to have a lot of cool new features, warp and wave. Then I looked closer and found that both are a no go for me.

Warp is closed source and you need to create an account to use your terminal. Jebus Christus, no, thanks, but no.

Wave is an Electron app. While that’s better than not having a Linux version, I’ve seen how Electron apps behave. They are the ones which hog all memory and get killed by the OS first. So that’s a no from me too.

I guess I keep my Tilix for now.

  • gomp@lemmy.ml
    3·
    8 days ago

    Might I add the idea that your terminal emulator must support your shell is utterly ridiculous?

    https://docs.waveterm.dev/reference/faq#what-shells-does-wave-terminal-support

    https://docs.warp.dev/getting-started/using-warp-with-shells

    Also Wave might be FOSS but if you look at the footer in their website it says it’s backed by venture capital… how would you estimate the chances it gets closed, paywalled or otherwise enshittified?

    • nous@programming.devEnglish
      1·
      8 days ago

      Might I add the idea that your terminal emulator must support your shell is utterly ridiculous?

      TBH I am starting to come around to the idea of a tightly integrated shell and terminal emulator support. There are just things you cannot do with these being separate things. I am very tempted to explore the idea from the other end though - writing a shell that has a emulator built into it (like screen/tmux basically are). But I do think that this integration is needed for any per command features that is not just printing out a prompt.

      It would be interesting to see what could be done with this type of integration but will likely break support for existing shells. Unless you maybe launch a shell for each command you run or something 🤔. Would like to seem more people experimenting with stuff like this and see what new things we could drive forward. We have been stuck with the current tty system since like the 80s to support devices that just dont exist anymore.

    • tehbilly@lemmy.dbzer0.com
      1·
      8 days ago

      By default, sharing a sudo password between PTY sessions is not allowed by your operating system. This can be a frustration when using Waveterm because every command is treated as a separate PTY session. To get around this, Waveterm will cache your sudo password in local memory (not written to disk) and share it with a session when provided.

      Holy crap, no thanks. That’s legit awful.