Hacker News new | ask | show | jobs
by PragmaticPulp 1806 days ago
FYI, this appears to be a startup launching an e-mail signup for a product that isn't available yet. Nothing wrong with that, of course, but it's worth noting up front. There is no download link and the GitHub link goes to an issues-only repo with no code.

There are several fast Rust-based, GPU-accelerated terminal projects that are open source and under active development:

Alacritty: https://github.com/alacritty/alacritty

Wezterm: https://github.com/wez/wezterm

Fig ( https://fig.io/ ) isn't Rust, but it's worth noting as a YC-backed competitor terminal product that has autocomplete similar to Warp.dev. Their website is eerily similar to warp.dev 's website, to the point where I can't help but imagine one was the inspiration for the other.

5 comments

> There is another fast Rust-based, GPU-accelerated terminal project that is open source and under active development:

I really thought 'Alacritty' came next! It's cool there are a few. If someone's looking for something popular and robust though, and not specifically interested in the cloud features of OP, Alacritty is pretty mature, actively developed, and also rust if you care.

Thanks! I forgot Alacritty was written in Rust. I added it to my comment.
With terminal emulators having already existed for decades, what benefits do Rust and GPU acceleration bring at this point? What problem are they solving? Not trying to sound confrontational, if I do, I’m just curious.
Cannot say too much about that since I only tried alacritty once, and from what I see it is mainly speed. And yes, that's actually noticable, at least on my machine.
I have not used the above terminal emulators, but I got a fast high refresh monitor (250Hz) with a 1000Hz keyboard recently, and the programs supporting 250 refresh/second does feel snappier. While it does feel snappier, it's not like I can press over 200 keys per second anyway, it's like with good sound, it's "night vs day" once you've paid for premium.
Well damn, i had no idea about Wez. I really miss Ligatures with Alacritty, so i should give Wez a try. Thanks for the link!
Also alacritty
Just tried it:

    2021-07-14T17:05:56.423Z WARN  window::os::windows::window    > EGL init failed with_egl_lib failed: with_egl_lib(libEGL.dll) failed: no compatible EGL configuration was found, atioglxx.dll: LoadLibraryExW failed, fall back to WGL
    2021-07-14T17:05:56.500Z ERROR wezterm_gui::frontend          > Failed to create window: The OpenGL implementation is too old to work with glium

I feel sad when terminals need OpenGL ... OTOH, apparently, my modest needs are adequately served by ConEmu on Windows and xfce4-terminal on Linux.
On the flip side, if you do have OpenGL, why not utilise it for unparalleled terminal performance? I've used Kitty for years for that reason, it's incredibly responsive and smooth, a pleasure to use.
What does a responsive terminal look like compared to something else? What are you doing with your terminal that demands responsiveness?

Genuinely curious. I've never ran into a situation where the standard terminals felt "sluggish"... barring a slow internet connection sshing.

You should look into Casey Muratori's quest[1] against Windows terminal slowness on github and youtube. There were some heated exchanges there and some proof of concept software created to demonstrate both how slow Windows Terminal is, and how fast a GPU enabled terminal can be.

[1] The latest video for it is here: https://www.youtube.com/watch?v=99dKzubvpKE

It's hard to describe, things just feel quicker. Scrolling through files in vim or tailing logs is super smooth, when your grep accidentally hits a huge json file that's lurking in your project it prints instantly instead of making the terminal unresponsive for a few seconds.

I used Urxvt for about fifteen years, it didn't feel slow at all. Kitty just _feels_ faster.

For one thing it's easy to build a bash line or even a NodeJS script that produces a lot of output that is dominated by the terminal's capability to render. When you benchmark it against the same thing but with a `foo > /tmp/foo.txt` redirection into a file, you'll notice that on bad terminals, it's several times or even orders of magnitudes faster than rendering to the screen. Many, many terminal emulators I have tried in the past did look sleek at first sight but then failed miserably a simple `cat manylines.txt` test.
Is kitty the one where it's really difficult to open two of them at once with different sizes and colors because those things can't be specified on the command line?
Well, that is kind of a given for a GPU accelerated terminal emulator, no?