Tbh I dont really see how anyone can call this bloat( I use doas btw). Its just so much more space efficient. 4 example I ported capitaine cursors and it takes below 200 kbs of space, its just that much more space efficient
You are most likely correct from a technical point of view.
But don't ever underestimate the potential of weird folks to be -- Weird.
Not that I think it's per se a bad thing -- But I feel like a lot of Linux people are pack bonded to the utilities and tools they have grown used to. Whatever justification they write comes after the fact from an emotional reaction to seeing the thing they are bonded with lose ground.
Sometimes I long back for the times when I just used my computer to do things, instead of forming an opinion about the compression rate of my cursor's image data.
I hope GTK and GNOME (or is GTK part of GNOME?) adopt this, I didn't even know just how bad the inefficiency with todays cursors is. Having a single svg for each cursor and rendering it server-side makes so much more sense.
One of the more interesting things I've read here. Very nice work. So long as it is free of vulnerabilities (with your small codebase, seems it should be) then this seems like a great addition. Hoping for widespread adoption.
Yo! I would love for something like this to become a thing because I have recently become a big fan of SVGs. Would absolutely love a custom cursor that scales to any size with minimal issues of it looking too small on the 1080 TV I sometimes plug my laptop into using HDMI.
Metadata
Some cursors cannot become SVGs, and that's fine. Some cursors are used for more than one shape, and that's fine. Some cursors are animated, and that's fine!
All of a shape's properties are described in a small meta.hl file alongside them.
Man, I've never thought about cursors at such a macro level before... Is the way it changes based on context of what it's hovering something really technical, or is there a call of some sort sent from the OS that is interpreted?