u0_a127 has quit [Read error: Connection reset by peer]
u0_a127 has joined #foot
rcf has quit [Quit: WeeChat 3.8]
rcf has joined #foot
pin56 has joined #foot
pin56 has quit [Remote host closed the connection]
pin56 has joined #foot
pin56 has quit [Remote host closed the connection]
pin56 has joined #foot
pin56 has quit [Remote host closed the connection]
pin56 has joined #foot
<rockorager>
dnkl: I was recently sent a significantly smaller lib than libsixel (https://github.com/seityaya/sixel_c), any advice on vetting vs libsixel? I have minimal knowledge of the edge cases
<rockorager>
Also as an aside...sixels are such a pain, I'm curious if you have considered kitty graphics at all, or have strong opinions either way
<rockorager>
IMO, the performance cost to an immediate mode TUI to support sixels is so massive it's just not worth it - supporting kitty or resolving to half/quartile block graphics is simpler than the world of sixels
<rockorager>
I think there is a valid use case for the primary screen, but on the alt screen it gets very difficult
<rockorager>
Anyways, these are many separate topics and I really only am wondering about the first question re: libsixel :)
cbb has quit [Quit: cbb]
alexherbo2 has quit [Remote host closed the connection]
alexherbo2 has joined #foot
u0_a127 has quit [Ping timeout: 265 seconds]
alexherbo2 has quit [Remote host closed the connection]
andyrtr_ has joined #foot
andyrtr has quit [Ping timeout: 246 seconds]
andyrtr_ is now known as andyrtr
pin56 has quit [Remote host closed the connection]
pin56 has joined #foot
pin56 has quit [Remote host closed the connection]