@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
@newt
> Rust and GPU use aren't selling points, they are mostly irrelevant technical details
They sure aren't selling points, but they also aren't "Rust… 🤮 meh, won't use" for me — that is what I mean. The term having AI assistant is sure superflurous, the fact that it's in Rust and has GPU acceleration is… Does it work well? Fine, okay!
@nik @scathach
@newt
> I'd probably continue with urxvt
I have a couple of very old ThinkPads lacking hardware EGL support and I'm using Xorg with st on them — no problem. I don't see the point in sticking with urxvt — it might seem minimal to some, but it isn't, in fact it has a bunch of legacy shit to make it compatible with some stuff from the 70s.
@nik @scathach
@newt
My patched st doesn't have all that, but it has stuff that's actually useful today: support for colour emojis that isn't messy and sixel graphics which makes w3m suitable for lightweight web browsing — urxvt doesn't, why would I prefer it? It seems to me that some go above and beyond to use some software just because it's old. Take Wayland, if your video doesn't work well — it's a solid reason not to use it, but on my hardware it works perfectly.
@nik @scathach
@newt
Why smear it with shit because it doesn't support exact window placement which makes using your commercial CAD uncomfortable if I don't need any of that.
If it just doesn't work for you — fine, but why would I avoid things implemented in Rust or Wayland if they suit me perfectly? 🤷
@nik @scathach
@newt@stereophonic.space @m0xee@social.librem.one @nik@misskey.bubbletea.dev @scathach@stereophonic.space
Rust isn't a selling point
Especially when the program would leak memory anyway.@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...
@newt
I personally doubt that it even uses any directly, I think it just relies on what Wayland provides.
> how is the bestest terminal today better than urxvt from 2003
Well, at least it can render colour emojis that do not leave traces when you're scrolling. Some can do neat shit like inline images with sixel — and it doesn't make the terminal slow.
@nik @scathach