• @[email protected]English
    14•1 year ago

    Not related to the article, but I really wish Warp was at least partially open source. If the client I was open I woule love to be able to use it without the feature online features.

    • @[email protected]
      1•1 year ago

      Last time I used warp it also wasn’t super customizable. I like messing with the prompt and stuff. I wonder if that’s changed. I did get a t-shirt from them for doing a user interview though :)

    • @MashedTech
      1•1 year ago

      Also warp is slooooow… And like I thought iTerm was fast and then discovered how much battery on my m1 Mac it was eating. I’m just a kitty user in the end with good zsh extensions managed by antigen(oh-my-zsh is bloated) and I’m living the good life.

  • @[email protected]English
    8•1 year ago

    Interesting read, thanks for posting. I hadn’t considered how predictive text works in a terminal emulator and its cool to see how that works as well as getting a better understanding of child processes and what commands would/wouldn’t start one

    • @btaf45
      4•1 year ago

      Unix loves to fork processes. So you get lots and lots of processes.

      • ParadoxEnglish
        4•1 year ago

        Only system I’ve used that loves processes more than Unix is Erlang

  • @[email protected]
    1•1 year ago

    This is a great deep dive! I am curious how difficult/slow it is to extend the modern xterm interface. For example, I saw that some terminals now support squiggly underlines for errors. What would it take to build a terminal (and associated interface) that supported things like text size? (Of course it would break a lot of applications that treat the screen as a two dimensional grid)