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

Rio: Terminal app built over WebGPU, WebAssembly and Rust

github.com

Post reply on HN
Print view View original

51–60 of 134 posts

Re: Rio: Terminal app built over WebGPU, WebAssembly and Rust

#51

Post by michaelmcdonald »

WesolyKubeczek wrote: post #49
tambourine_man wrote: post #40

Earlier quoted context omitted.

Apple didn’t get the memo it seems. Terminal.app has been unchanged in many, many years. I still stubbornly use it as my daily driver for some probably terrible reason.

With iTerm.app, getting a message that "your system ran out of application memory" is a reason for me to stick to the Terminal.app. It's a 96 GiB of RAM machine, for chrissake! That ought to be enough for everybody!

How on earth have you had iTerm use up so much memory it's given you an error? I've been using iTerm for years on some absolute crap machines, abusing iTerm with tmux and numerous customizations, and have never received that error.

Re: Rio: Terminal app built over WebGPU, WebAssembly and Rust

#52

Post by _joel »

WesolyKubeczek wrote: post #49
tambourine_man wrote: post #40

Earlier quoted context omitted.

Apple didn’t get the memo it seems. Terminal.app has been unchanged in many, many years. I still stubbornly use it as my daily driver for some probably terrible reason.

With iTerm.app, getting a message that "your system ran out of application memory" is a reason for me to stick to the Terminal.app. It's a 96 GiB of RAM machine, for chrissake! That ought to be enough for everybody!

That sounds very wrong to me, I used iTerm fine for years on 8GB

Re: Rio: Terminal app built over WebGPU, WebAssembly and Rust

#53

Post by fyrn_ »

brundolf wrote: post #41
stickyricky wrote: post #6

What's the implication of using WebGPU? Better terminals in the browser? Better electron terminals? A quirk for better native portability?

VSCode's terminal is rendered with WebGL (a cousin of WebGPU), since VSCode is an Electron app

WebGL is not really related to WebGPU in any way. WebGL is almost a strict subset of Gles3, WebGPU is a completely different API, sharing on a few concepts. They're about as related as Java and JavaScript

Re: Rio: Terminal app built over WebGPU, WebAssembly and Rust

#54

Post by natrys »

norman784 wrote: post #9

My question is what's their selling point, I used the past few years few terminals that have pretty good features: - Alacritty minimal and blazingly fast - Wezterm with batteries included - Warp even batteries included

Meanwhile I have to wonder what's the selling point of these over good old urxvt? It has an ecosystem of perl plugins, which has all the batteries I need and more. In its daemon/client mode I can have 20+ terminal windows open and they consume sum total of like 30MB memory, with embedded perl interpreter and everything. I feel like one or two instances of these modern incarnations is enough to completely dwarf that number.

GPU rendering is really cool, but I don't really understand what might people be doing where CPU rendering in terminal is anywhere close to being a bottleneck. People lose ability to comprehend way before that, why would I want gibberish to be printed even faster? Redirecting output to a file (or /dev/null) is almost always what I would want?

Re: Rio: Terminal app built over WebGPU, WebAssembly and Rust

#55

Post by folkrav »

WesolyKubeczek wrote: post #49
tambourine_man wrote: post #40

Earlier quoted context omitted.

Apple didn’t get the memo it seems. Terminal.app has been unchanged in many, many years. I still stubbornly use it as my daily driver for some probably terrible reason.

With iTerm.app, getting a message that "your system ran out of application memory" is a reason for me to stick to the Terminal.app. It's a 96 GiB of RAM machine, for chrissake! That ought to be enough for everybody!

I used iTerm on a 2011 iMac with 6GB of mismatched RAM until 2018 at work, and a crappy 2012 MBP with 4GB RAM (subsequently upgraded to 8GB) from 2012-2016 without issue. This is not normal at all lol

Re: Rio: Terminal app built over WebGPU, WebAssembly and Rust

#58

Post by 0x457 »

michaelmcdonald wrote: post #51
WesolyKubeczek wrote: post #49

Earlier quoted context omitted.

With iTerm.app, getting a message that "your system ran out of application memory" is a reason for me to stick to the Terminal.app. It's a 96 GiB of RAM machine, for chrissake! That ought to be enough for everybody!

How on earth have you had iTerm use up so much memory it's given you an error? I've been using iTerm for years on some absolute crap machines, abusing iTerm with tmux and numerous customizations, and have never received that error.

Unlimited scroll buffer + compiling something large with verbose logs non-stop?

Re: Rio: Terminal app built over WebGPU, WebAssembly and Rust

#60

Post by happens »

manaskarekar wrote: post #32
ilrwbwrkhv wrote: post #27

Earlier quoted context omitted.

Kitty has the lowest latency and is the best terminal in the market, but they are not on windows.

Kitty is my favorite but acts weird when ssh-ing into other machines for reasons discussed on their github. (To do with setting the $TERM correctly)

Had that problem for a while too, but you can actually really easily set the TERM variable for every ssh connection separately from your local TERM. Just put the following in your ~/.ssh/config:

  Host * 
     SetEnv TERM=xterm-256color
Post reply on HN