Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Waveterm

waveterm.dev

Post reply on HN
Print view View original

81–90 of 132 posts

Re: Waveterm

#81

Post by jzb »

IshKebab wrote: post #65
wiseowise wrote: post #34

Earlier quoted context omitted.

> Vim sucks. Why?

Two main reasons: 1. It has a ridiculous learning curve to get to the same editing proficiency as just having multiple cursors. All Vim users imagine themselves to be editing text at the speed of light while users of "lesser" editors struggle with scalar editing. I have seen zero evidence of that. Anyone of my colleagues that use Vim struggle to do basic tasks because remembering the gazillions of mnemonics is too on…

Vim isn’t for you, and that’s fine. Statements like “all Vim users…” aren’t really a great contribution to the discussion.

I’ve used Vim for 20+ years. I like it, you don’t have to. I don’t try to shove it down anyone’s throat - nor do I try to tell you why your favorite tool sucks. Because it probably doesn’t suck - for you. Tell me what you like or what doesn’t work for you and leave the middle school attitude where it belongs.

Re: Waveterm

#82

Post by behnamoh »

lijok wrote: post #75

Is anyone actually looking to use one of these "style over substance" terminals? Sure they look pretty at first glance, but instill significantly more cognitive load on the reader to understand what information it's trying to present. If people are really interested in using terminals like this, is there a business case to be made for incredibly visually-stylish programming languages as well?

I don't know. I feel like __some__ additional features in terminal would be nice. Like having the new vscode sticky scroll, incorporating a file manager like ranger into common terminals, being able to display long (CURL) commands in a more structured way (maybe a hierarchical tree that you can traverse), etc. I use Vim on Fish shell but it'd be nice to have Vim baked right in the terminal as well.

Re: Waveterm

#83

Post by lxe »

Why do I need to agree to the terms of service to run a terminal program?

Re: Waveterm

#86

Post by getoffmyyawn »

I don't know who this tool is for but it is certainly not designed for me. Unrelated but I recently learned the magic of

    vim scp://1.2.3.4/file_to_edit

Re: Waveterm

#87

Post by aumerle »

behnamoh wrote: post #80
jay-barronville wrote: post #73

I haven’t tried this yet (so please take my commentary with a grain of salt), but my initial thoughts are: (1) it looks interesting, (2) it looks overwhelming (there’s a lot going on in those screenshots), and (3) it’s likely slow (I might be completely wrong). To elaborate a bit… 1. I love good design work and well-designed (UI-wise) software, and it certainly looks like the creators of Wave Terminal have made that…

Tried Kitty for a few months. Didn't like the developer's attitude when people raised concerns and asked for "tabs". He said "just go use tmux on top of Kitty." I use tmux sometimes, but the idea that you have to glue together several pieces of software (each of which can break at any point) just to get basic functionality (like tabs that some people want) is insane. I stopped using Kitty and switched over to iTerm2…

Umm kitty has native tabs and the developer never tells anyone to tuse tmux, on the contrary he tells people not to use tmux. You are confusing kitty with alacritty.

Re: Waveterm

#88

Post by tssva »

krzyk wrote: post #76

Reading the page and encountering "web standards" got me thinking (red flag #1), why would I care for web standards in a terminal ? Another red flag is bashing vim. Final - looking at the code and seeing "electron".

"Another red flag is bashing vim."

The website in context of discussing their inline editor says, "Ditch vim for quick updates.". You seem to have a very low threshold for what is considered bashing.

Re: Waveterm

#89

Post by CharlesW »

krzyk wrote: post #76

Reading the page and encountering "web standards" got me thinking (red flag #1), why would I care for web standards in a terminal ? Another red flag is bashing vim. Final - looking at the code and seeing "electron".

> Reading the page and encountering "web standards" got me thinking (red flag #1), why would I care for web standards in a terminal?

In part, I assume that "powered by open web standards" is a euphemism for "built with Electron". It likely also speaks to its inline rendering support, its extensibility model, and its ability to leverage Monaco for code editing.

Re: Waveterm

#90

Post by wredue »

lxe wrote: post #83

Why do I need to agree to the terms of service to run a terminal program?

This is not the terminal for me, but it looks like a pretty typical “as is, no warranty, no liability, telemetry is collected” TOS.

Even if I was on the market for a slow, space wasting terminal, it appears venture backed, so enshitification is guaranteed making this terminal unusable from the onset.

Post reply on HN