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

121–130 of 134 posts

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

#121

Post by yakubin »

JdeBP wrote: post #118
yakubin wrote: post #114

Earlier quoted context omitted.

I don't see it here, but one example would be help messages saying "consider introducing lifetime `'bla` here", which are preceded with a source code quote saying something like: fn foo (...) According to cat -v , is preceded by ^[[38;5;10m, which, according to [1], "applies extended color value to the foreground", and further that 38;5; sets "foreground color to index in 88 or 256 color table". [1]: https://learn.mi…

Oh dear. You will I hope not be too embarrassed by learning that the 10 in SGR 38;5;10 (that control sequence) is colour index 10, which is less than 16, and a member of the very AIXTerm 16 colour set that you want. Thus the rust compiler is not in fact using a colour outwith the 16 AIXTerm colours.

Then I don't know how it happens, because I only have yellowish background + black and red defined in my terminal (also white, which I don't see used anywhere). And here is a screenshot from my Terminal.app, where the lifetime is gray: https://0x0.st/HqVq.32.png>.

I've checked and the 10th colour is set to #000000 in my Terminal.app settings.

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

#122

Post by esjeon »

BaculumMeumEst wrote: post #109
esjeon wrote: post #106

Earlier quoted context omitted.

This is anyway a niche market on Linux - you can go really far with gnome/kde default terminals, and even slimmer ones like xterm/urxvt/st are more than enough to perform all the necessary tasks. Perhaps, on Mac, you badly need an alternate terminal app , because the default one is unbearably slow.

> the default one is unbearably slow https://danluu.com/images/term-latency/loaded-terminal-laten...

[flagged]

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

#123

Post by tambourine_man »

yakubin wrote: post #116
tambourine_man wrote: post #110

Earlier quoted context omitted.

I think you can set how the terminal presents itself in both tmux and regular Terminal.app If the app doesn’t check for support and simply spills the control characters, there may be garbled output.

I've tried switching this setting in Terminal.app and all it seems to do is change the value of the TERM environment variable. I haven't observed any other effect.

It’s that value that apps should check. I know vim does.

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

#124

Post by tambourine_man »

JdeBP wrote: post #119
tambourine_man wrote: post #111

Earlier quoted context omitted.

I don’t know where or who we would address it to. “Feedback” is such a black whole.

Is Apple making Microsoft look good by comparison, again? (-: Microsoft Terminal has a whole open GitHub issues system to itself. * https://github.com/microsoft/terminal/issues/

Microsoft is all warm and fuzzy towards developers. Developers, developers, developers, and some old CEO used to say.

Apple seems to have forgotten we exist.

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

#125

Post by pxc »

BaculumMeumEst wrote: post #109
esjeon wrote: post #106

Earlier quoted context omitted.

This is anyway a niche market on Linux - you can go really far with gnome/kde default terminals, and even slimmer ones like xterm/urxvt/st are more than enough to perform all the necessary tasks. Perhaps, on Mac, you badly need an alternate terminal app , because the default one is unbearably slow.

> the default one is unbearably slow https://danluu.com/images/term-latency/loaded-terminal-laten...

Input latency might be good with Terminal.app, but it really chugs when there's a lot of output scrolling on the screen, especially if you use a terminal multiplexer. The last time I 'lived' on macOS, I had to ditch Terminal.app within a day, just from having a few apps compiling and printing logs in a tmux window.

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

#126

Post by JdeBP »

yakubin wrote: post #121
JdeBP wrote: post #118

Earlier quoted context omitted.

Oh dear. You will I hope not be too embarrassed by learning that the 10 in SGR 38;5;10 (that control sequence) is colour index 10, which is less than 16, and a member of the very AIXTerm 16 colour set that you want. Thus the rust compiler is not in fact using a colour outwith the 16 AIXTerm colours.

Then I don't know how it happens, because I only have yellowish background + black and red defined in my terminal (also white, which I don't see used anywhere). And here is a screenshot from my Terminal.app, where the lifetime is gray: https://0x0.st/HqVq.32.png >. I've checked and the 10th colour is set to #000000 in my Terminal.app settings.

If SGR 38;5;10 is not producing green, which it isn't, then it must be following your palette. My educated guess is that for some reason it believes that it should lighten the palette-specified colours from 8 to 15, and it's lightening your black to a very dark grey.

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

#127

Post by eschaton »

v3ss0n wrote: post #19
flashback2199 wrote: post #11

[flagged]

Yeah I still can't understand the point of requiring GPU for terminals. What webgpu needed is graphics drawing applications are most graphics drawing apps on web are still using canvas 2d or SVG, not even webgl. If we are to build a graphic heavy tool like figma - all choices we have are mostly SVG.

Also why do it in JavaScript in a web page? So much waste for something that literally didn’t require a CPU at all back when they were first created. (Terminals were originally implemented via state machines with pure logic.)

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

#128

Post by eschaton »

JaggerJo wrote: post #34

But.. why? Couldn't you just use Rust + OpenGL/SDL2/.. or even AppKit if macOS is the only supported OS?

Yeah, it’s yet another webshit forcing things into their preferred tech stack no matter whether it meets the needs of the problem domain or even whether the tech stack itself is sensible.

JavaScript doesn’t belong anywhere in anyone’s tech stack, and unless you’re making a web page neither do HTML or CSS.

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

#129

Post by inkyoto »

awestroke wrote: post #67
0x457 wrote: post #58

Earlier quoted context omitted.

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

Well just limit the scroll buffer then

Such advice is not helpful. The infinite scroll buffer is useful for some people with long lived terminal sessions, and that helps them with their respective workflows and habits. I am one of them.

The parent ran out of memory with iTerm not because of the infinite scrolling buffer but because of iTerm having memory leaks. The memory leaks in iTerm used to be a big issue, and it appears they still have not fully fixed. Other terminal apps can swell up to over 1Gb of the RSS, yet they do not crash. Provided there is sufficient RAM available, the inifinte scrolling can prove to be benefecial.

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

#130

Post by xcdzvyn »

eschaton wrote: post #128
JaggerJo wrote: post #34

But.. why? Couldn't you just use Rust + OpenGL/SDL2/.. or even AppKit if macOS is the only supported OS?

Yeah, it’s yet another webshit forcing things into their preferred tech stack no matter whether it meets the needs of the problem domain or even whether the tech stack itself is sensible. JavaScript doesn’t belong anywhere in anyone’s tech stack, and unless you’re making a web page neither do HTML or CSS.

> JavaScript doesn’t belong anywhere in anyone’s tech stack, and unless you’re making a web page neither do HTML or CSS.

Rio uses none of these things?

Post reply on HN