[beardicus]

In before the JavaScript gripes begin. How about we skip the Electron whinging this time?

I haven't switched to Hyper because I have found it a bit pokey and that doesn't work for me, but I'll still give this one a try. I'm curious to hear about any interesting reasons other people _have_ chosen Hyper, or particularly cool things it enables by being built on web technologies. Anybody?

[egeozcan]

> In before the JavaScript gripes begin. How about we skip the Electron whinging this time?

I have a feeling that it's used to farm hate (as karma or "acceptance"). In a less accusatory way, let me say, I think that people really like to see that other people share their hate. This is just my gut feeling though, as I don't share their passionate hate,even though I don't "love" electron.

[beardicus]

Update: Hyper 3 feels super-fast. Startup and new tabs are somewhat sluggish still but actual rendering responsiveness seems real nice.

[HereBeBeasties]

Sad commentary on the state of the world when you feel the need to comment on the speed with which a computer can pain text to the screen.

If you read their changelog you'll see that Hyper 3.0 uses WebGL to achieve this.

OpenGL. To draw text at a reasonable speed. It's not individually an insane thing to do within the context of Electron, etc. but take five steps back and talk about using a sledgehammer to crack a nut...

[iaml]

It's not insane. FYI the fastest terminal (alacritty) achieves its performance by rendering via gpu, and it's written in rust. iTerm recently started doing it too.

[nickjj]

But if you look at input latency benchmarks (there was one posted not too long ago on HN, maybe a month or 6 weeks ago) alacritty isn't close to the fastest terminal for pressing a key and being able to see the key on the screen.

IMO pressing a key and seeing it is the primary focus of a terminal.

[Fnoord]

Here is an output latency benchmark [1]

[1] https://github.com/jwilm/alacritty/issues/673#issuecomment-4...

[Tyriar]

I wrote the WebGL renderer after explorations in rendering the text using a 2D canvas which simply didn't live up to my expectations. It wasn't so much about drawing text at a "reasonable" speed, that was very easy to accomplish using the DOM, it was about excelling and trying to reach native-level performance from within a web context.

You can argue about the downsides of Electron all you want, but in xterm.js (the component that does the terminal parsing/rendering that Hyper consumes) we have a portable terminal frontend that can run on anything that has a webview and is getting really fast. It's also used in _a lot_ of software[0]. I wouldn't call that particularly sad.

https://github.com/xtermjs/xterm.js#real-world-uses

[ynniv]

Actually that's a very reasonable thing to do. macOS has been using hardware accelerated graphics since 10.0, and leveraging this is better than fighting it.

Also see https://github.com/jwilm/alacritty

[lprd]

+1 for Alacritty. I've been using it as my daily driver (switched from iTerm2) for a few months now and I couldn't be happier.

[kbd]

How do people use Alacritty as a daily driver when it can't open more than one window?

[intertextuality]

Tmux. Alacritty lacks basic things like splits or tabs so tmux or screen are recommended.

[Joe8Bit]

Same, I try it every few months to see if its tmux support has improved. So far no luck!

I actually really like the way it's configure/managed, the whole `hyper install foo` is pretty nice.

[nfRfqX5n]

been using it for over a year on my windows machine, never really had any issues. probably gonna try out the new microsoft terminal soon tho