# I am the Watcher. I am your guide through this vast new twtiverse.
# 
# Usage:
#     https://watcher.sour.is/api/plain/users              View list of users and latest twt date.
#     https://watcher.sour.is/api/plain/twt                View all twts.
#     https://watcher.sour.is/api/plain/mentions?uri=:uri  View all mentions for uri.
#     https://watcher.sour.is/api/plain/conv/:hash         View all twts for a conversation subject.
# 
# Options:
#     uri     Filter to show a specific users twts.
#     offset  Start index for quey.
#     limit   Count of items to return (going back in time).
# 
# twt range = 1 15
# self = https://watcher.sour.is/conv/qsinbiq
After having used st as my main terminal for a while now:

- Most things work just like in xiate, but I did patch st heavily. Took quite some time to do this, but it was also fun, so it was worth it.
- st uses much less memory than xiate (12-20 MB for st, 40 MB+ for xiate) – but *way more* CPU time. 😅 When I move another window on top of an st window (so that st has to do a lot of redraws), the CPU spikes so much that my whole X server begins to stutter.
- There’s no point in denying it: Font rendering is way better in xiate, because it can use the whole GTK-Pango-Whatever stuff. That’s a lot of code and could arguably be viewed as “bloat”, but the results are also better. Font stuff is not trivial, it’s inherently complex.
After having used st as my main terminal for a while now:

- Most things work just like in xiate, but I did patch st heavily. Took quite some time to do this, but it was also fun, so it was worth it.
- st uses much less memory than xiate (12-20 MB for st, 40 MB+ for xiate) – but *way more* CPU time. 😅 When I move another window on top of an st window (so that st has to do a lot of redraws), the CPU spikes so much that my whole X server begins to stutter.
- There’s no point in denying it: Font rendering is way better in xiate, because it can use the whole GTK-Pango-Whatever stuff. That’s a lot of code and could arguably be viewed as “bloat”, but the results are also better. Font stuff is not trivial, it’s inherently complex.
After having used st as my main terminal for a while now:

- Most things work just like in xiate, but I did patch st heavily. Took quite some time to do this, but it was also fun, so it was worth it.
- st uses much less memory than xiate (12-20 MB for st, 40 MB+ for xiate) – but *way more* CPU time. 😅 When I move another window on top of an st window (so that st has to do a lot of redraws), the CPU spikes so much that my whole X server begins to stutter.
- There’s no point in denying it: Font rendering is way better in xiate, because it can use the whole GTK-Pango-Whatever stuff. That’s a lot of code and could arguably be viewed as “bloat”, but the results are also better. Font stuff is not trivial, it’s inherently complex.
@movq So are you switching back then? Wasting RAM rather than CPU load is the lesser of the two evils in my book. At least in summer. :-)
@lyse I’m going back and forth at the moment, can’t make up my mind. 😅 Exactly, I’d rather waste RAM than CPU cycles in this case. Battery lifetime suffers, heat goes up, …
@lyse I’m going back and forth at the moment, can’t make up my mind. 😅 Exactly, I’d rather waste RAM than CPU cycles in this case. Battery lifetime suffers, heat goes up, …
@lyse I’m going back and forth at the moment, can’t make up my mind. 😅 Exactly, I’d rather waste RAM than CPU cycles in this case. Battery lifetime suffers, heat goes up, …
Applying a patch like this fixes a big part of the CPU issues that I saw:

https://lists.suckless.org/dev/1706/31857.html

This never made it into their master branch, there wasn’t even a proper discussion. Maybe nobody cares, because they’re all using nothing but dwm. 🤷
Applying a patch like this fixes a big part of the CPU issues that I saw:

https://lists.suckless.org/dev/1706/31857.html

This never made it into their master branch, there wasn’t even a proper discussion. Maybe nobody cares, because they’re all using nothing but dwm. 🤷
Applying a patch like this fixes a big part of the CPU issues that I saw:

https://lists.suckless.org/dev/1706/31857.html

This never made it into their master branch, there wasn’t even a proper discussion. Maybe nobody cares, because they’re all using nothing but dwm. 🤷
@movq Doing less is a good improvement.
After having applyed that performance patch, I’ve used nothing but st. It works just as fine for me as xiate does. The only thing that it doesn’t support is colored emojis – but come, they’re not *that* important (to me).

I’m beginning to think that xiate’s days might be numbered. I don’t want to worry about GTK shenanigans anymore.
After having applyed that performance patch, I’ve used nothing but st. It works just as fine for me as xiate does. The only thing that it doesn’t support is colored emojis – but come, they’re not *that* important (to me).

I’m beginning to think that xiate’s days might be numbered. I don’t want to worry about GTK shenanigans anymore.
After having applyed that performance patch, I’ve used nothing but st. It works just as fine for me as xiate does. The only thing that it doesn’t support is colored emojis – but come, they’re not *that* important (to me).

I’m beginning to think that xiate’s days might be numbered. I don’t want to worry about GTK shenanigans anymore.
@movq Sounds good.