5 ms·
Eh, not really. Main advantage of terminal stuff is near-zero dependency and working over SSH, if in addition to that it's pretty (in "more readable" way), why
by xani_ 4y ago
Eh, not really. Main advantage of terminal stuff is near-zero dependency and working over SSH, if in addition to that it's pretty (in "more readable" way), why not ?
Web UI in comparison is always sluggish, usually required extra login method (instead of just sshing into client, or having CLI client with credentials saved) and in modern days require hundreds of megabytes of deps to even make the JS to run it
- wruza 4y agoIirc you can ssh-forward a port to a remote localhost-only web server and visit local http://localhost:port http://localhost:port to use it. Something like `ssh -forward 2345:2345 -exec “http-server -p 2345 /path/to/mysite” myhost`, but with real options instead of my pseudo ssh cli. Don’t get me wrong, I’m not fond of the modern web either, but setting up something like a chat-like shell in a browser-over-ssh sounds like a pretty straightforward and lightweight job. Edit: correct args would be ssh -L 2345:server:2345 user@server '/home/user/bin/my-web-shell -p 2345'
- FullyFunctional 4y agoThat totally breaks the flow. I often spends hours working remotely over ssh+tmux, running Emacs, htop, etc. in a full-screen terminal. Having to suddenly switch to a Browser just to interact with a pretty UI is a terrible flow-breaking trade-off. (OT: and anytime I have to bring up a browser I for "some reason" end up distracted from what I was doing.) I do wish terminal graphics support was a little better. A terminal (like iTerm 2 [0]) that supports inline graphics allows your terminal to display plot etc in a graphical form without having to exit it. In MGR [1] this was the _only_ way to display graphics, even interactive, and I think it had a lot of merit. [0] https://iterm2.com/documentation-images.html https://iterm2.com/documentation-images.html [1] https://en.wikipedia.org/wiki/ManaGeR https://en.wikipedia.org/wiki/ManaGeR
- zokier 4y agoI wish there was builtin support for webapps that was at least as integrated as X forwarding is on ssh. Basically what I'm imagining is some standardized way of tunneling http in unix sockets, and then ssh setting up the sockets and some env var. Then when application connects to the socket ssh client would open new browser window similar to PWA. There are many flaws with such approach, webapps being often crappy being of course one of them. But the redeeming factor is that practically all the tech already exists, this would need just minimal glue to make it reality, while many other approaches are more of a pipe dream.
- nuancebydefault 4y agoI always think, these guys are wizards, when seeing their backtick and pipe laden commands. When i want to access a codebase via ssh, i simply boot vscode and search for ssh connect. Then I see the complete tree in seconds, can change files, can search with regexp, whatever without stackoverflowing (literally and figurative). The command to build (compile/link) and test is usually just typing make or so in the ssh terminal. As alternative to scp, i simply right click a file or directory that i want to transfer without thinking about slashes, root dirs, credentials etc.
- SCLeo 4y ago> Web UI in comparison is always sluggish At this point, I am 95% convinced that the reason web UI's are oftentimes perceived as sluggish is the easy access to custom animation/transition on the web platform. As a result, developers tend to overdo animations, or set the transition too long, resulting in a subpar experience.