sawka

6 ms·

1.
Fireworks in the CLI, Triggered by CLI Command – Happy 4th of July [video](youtube.com)
1 points by sawka 2y ago|1 comments
2.
by sawka 2y ago
Been hard at work on a new rendering engine for Wave Terminal ( https://github.com/wavetermdev/waveterm ). Coded up a quick proof of concept for 4th of July showing fireworks rendering in the terminal, triggered by a CL
3.
by sawka 3y ago
Interesting take! By implementing our UI in React, we're hoping to make it significantly easier and more accessible to write cross-platform terminal extensions (and renderers / apps for different types of content). One of the in
4.
by sawka 3y ago
Hah, 100% not a paid promotion, although it is kinda awesome that you think it is! We were thrilled with the coverage (our first article!) after we soft launched on /r/opensource.
5.
by sawka 3y ago
Hah, we did not come up with the headline :). Really the vision for Wave is to have an out-of-the-box excellent terminal experience that's consistent across all of the machines that you log into. We also bring cool new features to th
6.
by sawka 3y ago
Wave is a terminal, so you're free to use any editor you'd like, including vim, emacs or ed. We just provide another option for users who don't find vim or emacs very intuitive. I've used emacs to code for over 25 year
7.
by sawka 3y ago
Telemetry is completely optional and anonymous (and we provide a switch to turn it off when you launch the app).
8.
by sawka 3y ago
Wave uses electron for rendering, but a Golang backend for networking and heavy lifting. This gives Wave the ability to be cross platform and still efficient under the hood.
9.
by sawka 3y ago
We're looking into Wails! Definite benefits with tighter integration with Go (and we can ditch the node server).
10.
by sawka 3y ago
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.
11.
by sawka 3y ago
yes! would love to do this. the biggest issue is security and how to sandbox that html from the rest of the terminal. we have some ideas on how to do this (iframes, postMessage, etc.) that i think could work.
12.
by sawka 3y ago
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 sa
13.
by sawka 3y ago
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 do
14.
by sawka 3y ago
i think the terminal can be much better than it is today. i quit my job and started working on this full time after making the prototype because i was convinced that universal history, inline rendering, and persistent sessions just need
15.
by sawka 3y ago
ya, i love iTerm. been a loyal user for more than 10 years. that is until Wave of course :)
16.
by sawka 3y ago
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 i
17.
by sawka 3y ago
zsh support and international character support are our top two issues right now. I know the intl chars can work, we just didn't do enough international testing before launch. sorry to hear that it didn't work out of the box
18.
by sawka 3y ago
Would love to get any suggestions for what people would like to see rendered inline in the terminal. Things like graphs, audio/video streams, filesystem view (that supports drag&drop from your local machine), graphviz, pdfs. Mayb
19.
by sawka 3y ago
I used Discord for Wave because it is real-time, free, and has a lot of community and auto-moderation facilities built in. It also seems to scale well to large communities. Because you asked, I think it is fair game to share our discord l
20.
by sawka 3y ago
I hear you. That is a problem with a lot of (bad) UIs and why I think people love text-UI (because it is harder to screw up). First, I don't want to get rid of the text UI -- you can always render your commands using the traditional
21.
by sawka 3y ago
Haven't tested it myself, but some people have gotten it to run on Windows via WSL. We'll have a true Windows port at some point as well.
22.
by sawka 3y ago
a couple that have come up a lot in my talks with devs who use the CLI, but don't necessary live in it are: copy/paste, dealing with tmux, getting disconnected, using 'vi' remotely, having to setup prompts/colors&#x
23.
by sawka 3y ago
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
24.
by sawka 3y ago
https://waveterm.dev has some screenshots. Also checkout our twitter feed https://twitter.com/wavetermdev . I couldn't post the homepage as the main link because of a dup check on HN (someone unaffiliated
25.
by sawka 3y ago
Yes, and we own commandline.dev! I wanted, and got, the email address mike (at) commandline.dev :)
26.
by sawka 3y ago
thanks, appreciate it! you also get the award for first comment :)
27.
Show HN: Wave – Modern Open-Source Terminal (macOS and Linux)(github.com)
82 points by sawka 3y ago|90 comments
28.
by sawka 3y ago
not yet, but it will. using electron will let us get there quickly, especially if we base support on WSL. honestly it is more of a problem with packaging and testing at this point vs some underlying incompatibility. note that our windows
29.
by sawka 3y ago
we don't have parity with tmux yet. in terms of scripting and screen splitting, tmux is better. but, we will get there for most of the features, and i hope we'll be able to deliver those features in a more user-friendly and ac
30.
by sawka 3y ago
founder/creator here. unfortunately this got posted without us being able to provide the proper HN background information, but i'll try to respond here. we are committed to open-source. we are committed to providing a free termin

More ›