SVG is probably a better fit for this use case.
Absolutely... when available. But many companies/teams do not release SVG artwork. PNG material is much more commonly available, and actually works with these tools.
WebP supports both lossy and lossless compression.
WebP did not always support lossless compression. It's conceivable that the tools' developers made the decision before that.
Images on the web usually aren't large enough for this to make a significant difference, and it can sometimes be offset by the quicker download time.
That does not fit the use case of diagramming tools. They usually have comparatively few assets that are used multiple times in the same document. The larger the document, the more benefit lower CPU cost has. And I've seen LARGE diagrams.
libjpeg and libpng have had a number of CVEs too though.
Fair. I'm just speculating that it might be a contributing factor for the tools still not supporting the format.
Maybe because in those scenarios PNG offers sharper images, which is more important than compression when you have complex diagrams. Or because webp is more CPU intensive, and PNG gives better performance when rendering. Or because of CVE-2023-4863.
Good luck using webp in any kind of collaborative diagramming software.
Might want to widen the template by 1px so that the tip of the leaf is not between two pixels.
"Fry" can also mean "a very small fish."
Use -m and limit the build job's memory so it doesn't kill the docker daemon.
"~~tax cheats who bribe~~ us!" FTFY
Can't argue with "Because."
Zap-Em van, Men in Black.
Cast it into the fire so that even Sauron can't hack it.
Telecoms: "Oh no, if this legislation passes we'll have to -" clutches pearls "- negotiate on even terms!"