4 ms·

Why would I want to run a whole web browser for shell access? Hard pass.

• chrisseaton 5y ago
  Thing of the 'whole browser' as basically a GUI framework these days.
  • ziftface 5y ago
    I thought that peoples' reactions to electron apps was way overblown, and it certainly comes with benefits, like customizability. So I thought I'd try hyper shell on windows. It was unusable. I expected terminal windows to open right away but there's a really annoying delay every time you open a new one. Really, everything was slow. Maybe it was just my computer. I would definitely prefer to use a less capable terminal that's fast.
  • ur-whale 5y ago
    > Thing of the 'whole browser' as basically a GUI framework these days. An a very bloated one at that.
• mthoms 5y ago
  Because Clippy? https://github.com/Eugeny/tabby-clippy https://github.com/Eugeny/tabby-clippy :) Seriously though, I've got a potential use-case where I want to cobble together a few related scripts into an an ad-hoc REPL that supports HTML and image output. A key library I have to use is written in JS. Granted, this is my first time seeing Tabby so I'm not sure if it will work - just that I might see a use for it. I agree with your sentiment 100% though - this is way too heavy for a day-to-day shell.
• sigmonsays 5y ago
  I second the hard pass. My comments below oh my god, the .tar.gz is 90MB compressed, uncompressed its 265MB. The xterm source code is 7-8MB. We dont need a terminal 33 times the size of a basic terminal. While I entertain the idea of a terminal in a web browser, I dont believe it has the ability to capture the keyboard entirely for tmux, emacs, etc to work. I also think the use of a web based terminal is quite limited to specific scenarios. Perhaps it would be nice to connect to a k8s cluster on a remote machine.