@newt@stereophonic.space @scathach@stereophonic.space less resource consumption?
@newt@stereophonic.space @scathach@stereophonic.space ...on extremely different modern hardware with extra instructions designed for rendering things to a screen efficiently yes
@newt @nik @scathach
Font rendering in modern terminal is order of magnitude more complex than it was back in rxvt days, when it was about displaying rows and columns of monospaced characters. Alacritty is both GPU-accelerated and in Rust, and I just don't see how it takes insane amount of time to "initialise the GL context", it opens the instant I release the keys bound to opening a new terminal 🤷
@newt
I'm using Alacritty with Sway only — if your hardware isn't capable of EGL, you'd certainly experience issues earlier than opening the term.
> how does rendering your terminal on a GPU improve things?
I don't know, I've never ever done a side by side comparison myself, it just feels fast and I stumble upon reports of it being fast online all the time — and it is attributed to GPU acceleration.
@nik @scathach
@newt
I agree, there is nothing that would make me choose Alacritty over everything else at all costs, it was the first Wayland-capable term I tried, it was good enough and I stuck with it.
But again, it already exists, it's in Rust, it's "GPU-accelerated", and it's marginally faster — why not?
@nik @scathach
@iska
I still think you're confusing allocated virtual memory for actual RAM used by the process — although I've never seen Alacritty use a gigabyte of either.
Some of these terminals kept running for weeks (just look at that CPU time) and it's "terminal-heavy" software running inside those: gomuks, tut, vim — not just shell. 20 megabytes? Perfectly fine by me!
@scathach @newt @nik
@m0xee@social.librem.one @scathach@stereophonic.space @newt@stereophonic.space @nik@misskey.bubbletea.dev
I still think you're confusing allocated virtual memory for actual RAM used by the process
I'm not THIS stupid... Alacritty did in fact use over 1gb when I noticed high memory usage that day...