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

Use Alacritty instead of Termite

github.com

Post reply on HN
Print view View original

101–110 of 331 posts

Re: Use Alacritty instead of Termite

#101

Post by stuaxo »

reader_mode wrote: post #44
cookguyruffles wrote: post #12

Is there any indication of the energy impact using a GL context to render plain old text? These concepts seem incompatible in the context of a laptop, and who needs GL here when the bottleneck is biological. One of my favourite working modes is shutting down everything and just hacking away in vim, partly for distraction management but primarily because of battery.

Why would GL rendering be any less efficient ? You don't have to rerender the entire screen in GL or render at MAX FPS if nothing changed.

It may or may not be - it certainly should be tested.

Re: Use Alacritty instead of Termite

#102

Post by warmwaffles »

fullstop wrote: post #79
jchook wrote: post #67

Earlier quoted context omitted.

The maintainers would prefer to "do one thing well" and let other programs handle this sort of feature. You can use tabbed[1] or a multiplexer like tmux, or you can use a different terminal emulator like kitty[2]. For example, instead of launching `alacritty`, you would launch `tabbed -c alacritty --embed`. 1. https://git.suckless.org/tabbed/ 2. https://sw.kovidgoyal.net/kitty/

tmux doesn't cut it for me. I use tmux on remote machines and really don't want to nest tmux sessions, and it looks like tabbed will spawn an alacritty process per tab. Kitty it is.

It also depends on your window manager too. I use BSPWM and tabs just always felt off when I could quickly flip to another workspace.

Re: Use Alacritty instead of Termite

#103

Post by zxzax »

traverseda wrote: post #100
zxzax wrote: post #86

Earlier quoted context omitted.

Again if you actually read the bug report, it contradicts what you're saying. This patch was rejected because it created unnecessary work for terminals outside the GNOME project. The favored solution would help all terminals using that widget.

Did they ever implement that solution?

It doesn't look like it, I'm sure they would be open to patches to help out there.

Re: Use Alacritty instead of Termite

#104

Post by zests »

enriquto wrote: post #81

I have no beef with gtk/gnome and the like, but I find it really funny when developers use such colorful language. Still, as a heavy terminal user, I fail to understand what's the big deal with the choice of terminal. I have used only xterm for more than 20 years (with a short stint with gnome-terminal, and I didn't find any relevant difference). It starts instantaneously and doesn't make any fuss while it's running.…

Many terminals lack ligatures. Once I started using a monospace font with ligatures I could never go back.

Re: Use Alacritty instead of Termite

#105

Post by simion314 »

jhasse wrote: post #92
simion314 wrote: post #71

Earlier quoted context omitted.

And now Qt, Electron, games , old programs will need to do extra work to satisfy a GNOME designer ego. you could always tell the window manager not to paint the decorations and you could have your own cool decorations (using a library if you want). From my point of view this looks that GNOME is force pushing their vision to all their users and all GTK users unfortunately.

Electron uses Gtk and Games should use SDL2. They will support CSD, which is work, but it will happen. You could also say that SSD would mean that Mutter needs to do extra work just to satisfy an application designer ego. Btw: I'm a GNOME user who is against SSD.

The issue is that Electron and SDL will fix this 10 years later, old apps will still not work.

Same issue with tray icons, GNOME is expecting cross platform apps will use their shirty design OR their users will use only new GNOME apps.

>You could also say that SSD would mean that Mutter needs to do extra work just to satisfy an application designer ego

Is better that say all the 10 WM implement SSD (maybe as a fallback for old or non native apps) rather then force all toolkits and old apps have to implement this how they think (won't you get apps that will look like XP or OSX because you forced the app to paint the buttons). As a developer myself feels rather stupid not to just provide the SSD for old apps , really feels like "let's make this old and non native apps look and work like shit so people use my cool design.

But I could see an argument that GNOME devs are not that competent though, they implemented a shell that will kill all your apps if there is an error in an exception(on wayland)... so incompetence could explain why they are not capable to provide both SSD and CSD too.,

Re: Use Alacritty instead of Termite

#106

Post by Cloudef »

zxzax wrote: post #98
Cloudef wrote: post #59

Earlier quoted context omitted.

>There are several Wayland compositors that don't implement that feature. Can you list some that aren't weston or dead projects?

I don't follow all the Wayland compositors but Enlightenment doesn't, and Weston matters here. If somebody really wants this to become standard, implementing it in Weston should be priority. Every compositor library I've looked at also considers this optional, e.g. mir, qtwayland, wlroots.

Considering it got xdg prefix and was included in wayland-protocols that should be as standard as it gets. Weston is barebones "reference" compositor. It's not for normal use. Mir is dead. The xdg-decoration is based on KDE's own protocol, it was later refined and pushed to wayland-protocols by wlroots devs. Now kde uses the xdg-decoration too.

>Every compositor library I've looked at also considers this optional

Because that's the point of it. If compositor doesn't implement it, application would have to fallback to CSD (however very inconvenient for many apps, or users who suddenly will not see a decoration due to purely _technical reasons_), and even when it's implemented, application have to explicitly ask for compositor to decorate the window.

Re: Use Alacritty instead of Termite

#107

Post by traverseda »

zxzax wrote: post #94
traverseda wrote: post #80

Earlier quoted context omitted.

As a programmer Gnome has really damaged their relationship with a lot of developers. For example take a look here: https://trac.transmissionbt.com/ticket/3685#no1 >I guess you have to decide if you are a GNOME app, an Ubuntu app, or an XFCE app unfortunately. I'm sorry that this is the case but it wasn't GNOME's fault that Ubuntu has started this fork. And I have no idea what XFCE is or does sorry. Gnome kind of goe…

Your first link is an issue that was posted over 10 years ago and was long resolved in other areas. It's not an illustrative example. I really wish people would stop trying to revive these ancient flamewars without acknowledging the current state of things (not saying this is your fault, but a little diligence always helps). The second two links you're posting are again, the exception, not the rule. The vast majority…

> It's not an illustrative example.

What I'm describing is a cultural problem. If you don't think that link is illustrative than you don't understand what it is I'm trying to illustrate.

Re: Use Alacritty instead of Termite

#109

Post by fullstop »

bitwize wrote: post #63
abrowne wrote: post #45

Earlier quoted context omitted.

It's Wayland-only, right? Alacritty OTOH not only works on X11, but is cross-platform.

X11's been EOL'd, dude.

I keep going back to X11 for various reasons. I was close last time, but google chrome still has various problems with wayland if one has more than one window open. I know that this is a chrome bug, but it ruins the experience and for this use case I can not use Firefox.

Re: Use Alacritty instead of Termite

#110

Post by thayne »

bhaak wrote: post #3

> GTK and most of the GNOME project are much of the same. Avoid them and don't make the mistake of thinking their libraries are meant for others to use. Choose your dependencies wisely. Sometimes only a crystal ball would have helped but often, a little bit of due dilligence would have prevented lots of upgrade pain down the line.

Sadly, I don't know of a good alternative to GTK. Qt, being C++ is more difficult to bind to from other languages, and doesn't seem to integrate quite as well with XDG/Linux standards, unless you use KDE which is a much heavier dependency.
Post reply on HN