Live data from Hacker News

Waveterm

waveterm.dev

31–40 of 132 posts

Re: Waveterm

#31
post #17
post #16

Neat, you can setup SSH connections as native terminal sessions. When you type in your server info and click connect, this happens: prompt> connecting to user@host... prompt> error connecting to remote: mshell client not found prompt> trying auto-install prompt> installing mshell v0.3.0 to user@host... Install something on a server without even asking? Also, what is "mshell client" or "mshell v0.3.0"?

Not to shill, but WezTerm can also do this and isn't built on web stacks, if anyone is looking for something similar.

And not backed by venture capital.

Re: Waveterm

#32
It's Electron/TS based. I seriously doubt I can get used to using an Electron based beast for something as critical as a terminal.

This is the one power user app where speed is factually of utmost urgency, and latency is non negotiable. I also don't like it using tons of memory. While this may be possible with Electron from what I have heard, I have yet to have seen it. So generally I stay away.

Re: Waveterm

#33

But like…why? At the risk of being “HN talks about rsync on the Dropbox thread” what’s this offering that can’t already do, for free, without a EULA, and inevitable VC-enshittification risk? > ditch vim for quick updates Bruh, have you seen the average vim user? They’re about the fastest people on a computer I’ve seen in my life. This is not exactly a convincing argument. > Render code, images, markdown, and CSV file…

It feels like it's for developers using VSCode, who are not comfortable with a terminal. It is likely meant to be easy-to-use with a mouse-friendly user interface and lots of built-in functionalities.

Re: Waveterm

#34
post #8

This looks nice! Editing in a proper editor is for sure nicer than Vim - does that work even over SSH without having to install anything? Proper history search also sounds nice. I think I will probably stick to VSCode's integrated terminal tbh because it's well integrated. But if I was doing system admin rather than programming this looks awesome. Don't listen to the predictable HN nonsense. Electron is plenty fast e…

> Vim sucks.

Why?

Re: Waveterm

#35
post #9
post #7

An Electron terminal with a EULA backed by two venture capitals. What's the world coming to? I'd rather keep something as crucial as a terminal emulator open-source, and with a latency within the hundreds of milliseconds. For the fancy remoting capabilities there's Emacs.

I use VSCode's integrated terminal all the time and its performance and latency is indistinguishable from Gnome Terminal. This appears to be open source. But I don't know how you could make a viable business out of this. I mean it looks nice, but nice enough to pay for? I doubt it. And it's free... What's their business plan?

> What's their business plan?

"telemetry"

Re: Waveterm

#36
post #7

An Electron terminal with a EULA backed by two venture capitals. What's the world coming to? I'd rather keep something as crucial as a terminal emulator open-source, and with a latency within the hundreds of milliseconds. For the fancy remoting capabilities there's Emacs.

I hope your vim doesn't take hundreds of milliseconds for anything, other than possibly opening huge files.

I said I want a latency within the hundreds of milliseconds. vim and most terminal emulators are well within this threshold, a very complex UI in Electron is not.

Re: Waveterm

#37
post #36

Earlier quoted context omitted.

I hope your vim doesn't take hundreds of milliseconds for anything, other than possibly opening huge files.

I said I want a latency within the hundreds of milliseconds. vim and most terminal emulators are well within this threshold, a very complex UI in Electron is not.

[flagged]

Re: Waveterm

#38
post #32

It's Electron/TS based. I seriously doubt I can get used to using an Electron based beast for something as critical as a terminal. This is the one power user app where speed is factually of utmost urgency, and latency is non negotiable. I also don't like it using tons of memory. While this may be possible with Electron from what I have heard, I have yet to have seen it. So generally I stay away.

Actually - VSCode comes with a built-in Terminal that's also built using Electron and TS.

Never had any issues with it while using it as built-in Terminal from time to time.

Re: Waveterm

#39
post #32

It's Electron/TS based. I seriously doubt I can get used to using an Electron based beast for something as critical as a terminal. This is the one power user app where speed is factually of utmost urgency, and latency is non negotiable. I also don't like it using tons of memory. While this may be possible with Electron from what I have heard, I have yet to have seen it. So generally I stay away.

I’m not the biggest fan of electron generally speaking but I don’t agree with your argument that Electron is too slow to work as a terminal emulator. Yes speed matters, but not nearly as much as you claim. Commands are run as separate processes so as long as the terminal reads from its PTY fast enough not to block those processes, which in all bar a very few edge cases it will be, you’re not going to experience any difference in performance.

Besides, if you’re concerned about millisecond latency, then the issue you actually have is with multimedia content being rendered in the terminal rather than Electon itself. So no terminal emulator of this generation is going to meet your needs irrespective of what technologies it’s built from.

Edit: downvoted for stating a fact. Maybe I should have also stated that I’ve also been working on this exact problem. In fact I’ve already got a shell that provides the CLI parts and been playing around with different technologies to handle the multimedia parts of the terminal emulation. It’s a harder problem to solve than people hand wave away when they complain about electron (hence why I only have a shell available for public use at this stage).

Re: Waveterm

#40
post #17
post #16

Neat, you can setup SSH connections as native terminal sessions. When you type in your server info and click connect, this happens: prompt> connecting to user@host... prompt> error connecting to remote: mshell client not found prompt> trying auto-install prompt> installing mshell v0.3.0 to user@host... Install something on a server without even asking? Also, what is "mshell client" or "mshell v0.3.0"?

Not to shill, but WezTerm can also do this and isn't built on web stacks, if anyone is looking for something similar.

Wezterm rules…
Post reply on HN