Live data from Hacker News

Waveterm

waveterm.dev

41–50 of 132 posts

Re: Waveterm

#41
post #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.

The VSCode terminal is the first time I've felt input lag in a terminal emulator before. When a program shits out thousands of lines of text (like catting a long log file), it takes forever to catch up compared to any other terminal (except the JetBrains builtin terminal, which is almost as slow but still noticeably faster).

Re: Waveterm

#44
This looks cool and I could get over my worries about Electron as a terminal except for the fact that it requires that you install something on the remote machine to get any of the benefits. I really don't like that it tried to do that before I had done anything but add a connection (there was no warning or indication that something would be installed).

Thankfully (?) FreeBSD is not supported so nothing was installed but I was still surprised that it even tried without some kind of prompting, ideally with "ask me each time" or "install automatically" options.

The terminal I use can't go dropping software on boxes I connect to (literally hundreds), I guess I'll stick with iTerm 2.

Re: Waveterm

#45
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 a fan of Electron either, but I don’t see how latency and resource usage are any more important for a terminal than other apps, like editors or messaging apps or email etc.

Re: Waveterm

#47
This looks nice, but I am very, very, very wary of adopting a tool like this without understanding the business model. There are two possible ways I've seen this go:

1) Build out a userbase. Once it's sufficient, monetize by screwing the userbase over in some way.

2) Take a bunch of VC money to build something awesome and open-source. Implode when there is no business model.

I'm glad this is open-source -- that's prerequisite -- but half of open-source is about transparency. The web site should clearly explain who built this, why, and how they plan to pay the bills.

This could be sleazy and evil or good. If it's good, explaining that generally provides business value, so most good players will do it proactively. A missing explanation is a yellow flag pointing towards "sleazy and evil."

I understand this is version 0, so please take this as constructive feedback and not an attack. This is my perception as a potential customer, and I hope it provides some value.

Re: Waveterm

#48

This looks cool and I could get over my worries about Electron as a terminal except for the fact that it requires that you install something on the remote machine to get any of the benefits. I really don't like that it tried to do that before I had done anything but add a connection (there was no warning or indication that something would be installed). Thankfully (?) FreeBSD is not supported so nothing was installed…

I liken this more to how vscode operates. I use that to develop remotely inside a vdi (or inside a local vm over ssh). It will install an instance of itself on the remote host and then it's like I'm operating "locally" out of that host. For work, I use one vm for all my development. For personal, I have a desktop computer I dedicate to development that I often access remotely via laptop/vscode.

But I wouldn't use vscode to connect to all the random hosts I need to throughout, especially if it's going to drop software.

Where I might consider a tool like is is if I connected to something along the lines of a jumpbox. Some primary host from which I launch most of my other work out of. Once it opens on that jumpbox, I could then ssh out from there. That would possibly make the session sidebar useless - unless I had a "jumpbox" per client/region/project.

Re: Waveterm

#49
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.

[deleted]
Post reply on HN