3 ms·

Your assumptions as presented in the article are somewhere between wrong and irrelevant. The rest of the article and what you are trying to build is somewhere b

• salt-thrower 5y ago
  Spot-on. The "problem statement" the author makes is woefully out of touch. I don't think it's too negative to take issue with the tone and inaccuracy of OP's article. I'd love to be interested in a new type of terminal, but not if the author has to trash existing terminals with demonstrably false statements.
• yunohn 5y ago
  Note: Prefacing this by saying Warp may not be a panacea, but terminals definitely need to be revamped. > Developers do not work in teams for the work they do in terminals. A lot of HNers might be lone wolves, but mentoring juniors and working with cross-functional team members definitely requires sharing terminal sessions. > It does not disappear, for every common configuration I'm aware of. The history persists. Commands history persists, within your machine, not necessarily across machines or environments usually (unless you’ve setup elaborate config for that). But more importantly, I often find my self hoping that output history for each command could be saved too - so I know what happened, what went wrong/right last time, etc etc. > This is completely irrelevant and misleading for something you actually do on one machine. Again, it’s not easy to carry over configuration and tooling across machines. Very often, machines I ssh into are missing a lot of my custom config and it’s a pain to re-adapt in the thick of it. > The most complicated thing I do with terminals is to type text. IME it super painful to build a shell config that works across Mac/Win/Linux that reliably does word selection, jumping, home/end, etc. I sorely miss all these shortcuts that I easily get in my text editor or IDE. > pressing tab already offers because of the descriptions Exactly that though. Autocomplete hovering and providing context is way easier than typing part of the command and pressing tab again and again to see if the completer finds anything.
  • onli 5y ago
    At least you might be way more their target group than me :) I'm not a lone wolf developer (currently), but sharing terminal sessions really never happens. Collaboration is done via chat/video and if something is shared on the screen, it's the IDE. Ah, and with git of course. Maybe that changes with a more dev ops oriented role, which is definitely not mine. > Very often, machines I ssh into are missing a lot of my custom config and it’s a pain to re-adapt in the thick of it. I - and I get the impression that's true for many developers - learned early to minimize the custom config. It's bash, maybe with tmux (or likely just screen) and some sensible defaults, and that's it. > IME it super painful to build a shell config that works across Mac/Win/Linux that reliably does word selection, jumping, home/end, etc. But why would one need that? Is your environment that random?
    • drewgross 5y ago
      Not OP, but a fan of Warp. > I - and I get the impression that's true for many developers - learned early to minimize the custom config. I get the exact opposite impression. My understanding is that as developers become more experienced, they tune their setup more, and have more and more persisted customizations. I consider sshrc[1] a critical part of my workflow for this reason. > But why would one need that? Is your environment that random? Most shells by default will occasionally spew out "garbage" text into the terminal like ^[[A. If you know why this happens it's possible to fix, but it's definitely a pain. Personally I consider it very important that all the places that I input text work consistently (e.g. move cursor by word, move cursor to end of line) and Warp providing that is a huge selling point to me. [1] https://github.com/danrabinowitz/sshrc https://github.com/danrabinowitz/sshrc