I tried it, it’s nice overall, I thought it’s CPU intensive but it turned out it’s because I have htop running in wave terminal, running it outside however seems to be normal.
My only criticism would be the UI, it’s clunky and I loathe the side-menu design in sites let alone in my everyday terminal, especially when there’s a menu on top already, and the logo is there despite if you tried to hide the menu, additionally, the whole “prompt-looking” design at the bottom isn’t great either, would prefer to have it on top and the history just go on the bottom instead, but those are my personal preference from 5min test.
Show HN: Wave – Modern Open-Source Terminal (macOS and Linux)
61–70 of 93 posts
Re: Show HN: Wave – Modern Open-Source Terminal (macOS and Linux)
#62Earlier quoted context omitted.
It absolutely should not be running commands on a remote host without prompting first!
agree in principle, but i will split some hairs here. if you type "ls" into your local terminal, there's an implicit agreement that it will run the remote "ls" program. the helper program facilitates that in the same way that any other terminal + ssh + shell combo does. it only runs commands in response to your activities in the terminal.
yes
if ls is installed on the remote host
and if it is not, the command should fail
this appears to be about telemetry, pure and simple
Re: Show HN: Wave – Modern Open-Source Terminal (macOS and Linux)
#63Earlier quoted context omitted.
agree in principle, but i will split some hairs here. if you type "ls" into your local terminal, there's an implicit agreement that it will run the remote "ls" program. the helper program facilitates that in the same way that any other terminal + ssh + shell combo does. it only runs commands in response to your activities in the terminal.
yes if ls is installed on the remote host and if it is not, the command should fail this appears to be about telemetry, pure and simple
absolutely no telemetry in the helper, full stop. you can inspect the code yourself.
we do hear the feedback though and are working on a popup/notification that will prompt you before we push the helper program for the next release.
Re: Show HN: Wave – Modern Open-Source Terminal (macOS and Linux)
#64Honest question, why does everyone uses discord for community space nowadays? What happened to product forums that could be easily found in a web search?
You can set up a Discord server for free in under 3 minutes. 10 if you want to install all the fancy moderation bots and change the icons and add custom emojis. There's nothing comparable for forums. FB tried but it's a cesspool of "user engagement", managing groups is a full time job and still doesn't work properly. Oh, and Discord _has_ a forum-like feature inside it :D
> Discord _has_ a forum-like feature inside it
Pretty sure the last bit in the GP was the important one:
> What happened to product forums _that could be easily found in a web search_?
Without web searching capability, whatever "forum-like feature" exists is still subpar.
Re: Show HN: Wave – Modern Open-Source Terminal (macOS and Linux)
#65> What if your command line terminal could display more than just text? That’s crazy right (I can hear the screams of thousands of graybeard sysadmins). The screams are because they remember the last... 3 or 4 off the top of my head? terminals that said that, and then fell over when you tried to cat a log file because they were using javascript in the hot path for displaying text. So how's your performance and respon…
All of the tty processing, networking, and stream processing is done in Go, so it is fast. There is obviously more performance work to do, but in some situations our model can actually be faster than other terminals. If you cat a 1GB file in Wave, it actually runs quickly because the frontend can drop frames, while the Go backend is buffering the stream (so to answer your question, JS is not in the hot path, only Gol…
> the frontend can drop frames, while the Go backend is buffering the stream
Surely that's not great. Dropped frames are terrible for following what's happening on the screen and even worse for scrolling.
Re: Show HN: Wave – Modern Open-Source Terminal (macOS and Linux)
#66> We’re proudly built on Electron (just like VSCode, Slack, and Discord) with all of the network code and heavy lifting done in a local Go backend. This enables us to deliver a consistent cross-platform experience and the ability to leverage high-quality web components for our UI and plugins. For my curiosity, why electron in a day when Tauri exists, or Wails since you seem to already be in the golang ecosystem?
We're looking into Wails! Definite benefits with tighter integration with Go (and we can ditch the node server).
Re: Show HN: Wave – Modern Open-Source Terminal (macOS and Linux)
#67Earlier quoted context omitted.
ya, i love iTerm. been a loyal user for more than 10 years. that is until Wave of course :)
For me iTerm was definitely too slow, alacritty is IMO a bit faster. Also heard some good things about Kitty, but that has too many bells and whistles for me. But nothing can beat foot [0]. But it's only for wayland, so I need to use alacritty on macOS. [0] https://codeberg.org/dnkl/foot/
Just in case you haven't tried it and want another option, Wezterm runs anywhere and does pretty much everything. But not AI/webapp stuff.
Re: Show HN: Wave – Modern Open-Source Terminal (macOS and Linux)
#68Earlier quoted context omitted.
the helper program is completely open source (waveshell) it is similar to the shell scripts or additions to your rc files that other modern terminals might add when connecting to a remote machine to support advanced features. the helper does not need any additional permissions, does not open any ports, runs only for the duration of the connection, and communicates exclusively via stdout/stdin over your standard ssh c…
It absolutely should not be running commands on a remote host without prompting first!
i don't see any difference between this and what saltstack or ansible are doing. both can run a command on remote machines, and to do that they automatically connect to the machine and copy a program to be run there.
Re: Show HN: Wave – Modern Open-Source Terminal (macOS and Linux)
#69Earlier quoted context omitted.
All of the tty processing, networking, and stream processing is done in Go, so it is fast. There is obviously more performance work to do, but in some situations our model can actually be faster than other terminals. If you cat a 1GB file in Wave, it actually runs quickly because the frontend can drop frames, while the Go backend is buffering the stream (so to answer your question, JS is not in the hot path, only Gol…
> the frontend can drop frames, while the Go backend is buffering the stream Surely that's not great. Dropped frames are terrible for following what's happening on the screen and even worse for scrolling.
mosh is also dropping frames if it needs to. only happens when the network speed can't keep up with the data being sent through
Re: Show HN: Wave – Modern Open-Source Terminal (macOS and Linux)
#70Earlier quoted context omitted.
i'd love to figure out what is causing this as we haven't been able to repro it. if you don't mind adding a comment to the issue with anything novel or interesting in your .bashrc / .bash_profile or your machine setup it would be much appreciated.
As macOS uses zsh by default, does waveterm do this too? As you ask for the bash files instead of the zsh files.
Zsh is not yet supported, it's very high on our list of priorities!