I wrote a TV guide app for Blackberry many years ago, and for the parts of the grid where the data had not yet downloaded, I drew (in code) a light checkerboard background like this. Got into a long-running argument with my company’s UX guy over it because he said it was a visual element that implied transparency when there wasn’t actually any transparency. So pointless - it wasn’t an app for image manipulation in the first place. I gave the darker squares a light blue tint and he left me alone, and then Blackberry died a quick death anyway.
The moral of the story is one that I took to heart for all my future mobile development: nothing matters, just go home and smoke another bowl.
Some real wisdom in this one.
Eh I’d agree with the UX guy. We get away with a lot flexibility in software dev that we can’t in other engineering, like mechanical or civil
On PC you can often drag an image before you download it.
You’ll see if it’s really transparent or just with a checkerboard pattern.This may be my favorite meme of this template. Wow.
It’s beautiful
I like this one:
Sync for Lemmy decided to absolutely destroy the quality of your image so I thought being unable to read it was the joke, but I still decided to spend what ended up being WAY too much time to figure it out from the few pixels available… and then I accidentally tapped on it and the normal readable version opened. This multilayered brain fart and subsequent realization humbled me in an odd way, feels weirdly good.
Here’s what it looks like:
It happened to me just a few weeks ago!
This is one of those memes that divides people. I’m proud to say I’m on the side who guffawed loudly and drew glances from strangers.
I thought this one was a quality joke for sure.
I’m chuckling on the toilet myself
transparent
What a .svg
We’re not saying svg is bad, are we? It’s vector graphics which is great for scaling your images. (For non-photo images)
The pun is “what a savage”
Oh hahaha, thanks for this
It downloaded in webp. Shit.
What’s wrong with WebP? It’s a modern format with smaller file sizes, and most software supports it. It’s very commonly used online these days instead of the legacy formats.
Good luck using webp in any kind of collaborative diagramming software.
Why does that software not support modern formats though?
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.
PNG offers sharper images, which is more important than compression when you have complex diagrams
WebP supports both lossy and lossless compression. Diagrams should use lossless compression so the image does not lose any quality.
PNG gives better performance when rendering
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.
because of CVE-2023-4863.
libjpeg and libpng have had a number of CVEs too though.
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.
WebP did not always support lossless compression. It’s conceivable that the tools’ developers made the decision before that.
WebP was first released in 2010, and lossless support was added in 2011. I really doubt there were tools built between 2010 and 2011 that haven’t been updated since then.
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.
SVG is probably a better fit for this use case.
I download memes to share them. Messenger does not like webp. It literally won’t allow me to send the image. I then have to edit the image just so I can send it. Now I have two copies of the same meme.
Which messenger? Signal and WhatsApp support it.
Edit: saw your reply below, it’s Facebook Messenger. Yeah, that’s a whole other problem of its own.
Google voice iirc still doesn’t support webp.
Might be a fine standard but support is shit ime. I’d prefer everyone just take up jpeg xl.
Google docs and sheets don’t support WebP either. Always ironic when they made the fucking format
Just rename it into a .jpg extension instead
Seems to just work for what i need them for ¯_(ツ)_/¯
Ive had one or two that didn’t but i could open then in gimp and export that way.
Just rename it into a .jpg extension instead
Seems to just work for what i need them for ¯_(ツ)_/¯
This usually means the app supports WebP but is doing something dumb like not allowing the WebP file type but not the .webp file extension. If that’s the case, it’s often a one-line code fix.
I thought WebP was fixed in Messenger a while back. You mean Facebook Messenger, right? I’ll see if I can figure out what’s up.
Photoshop only recently supported webp natively. Windows barely supports webp.
Inb4 “have you heard of linux”
is “recently” less than 15 hours ago because that’s when the comment was made
AFAIK Windows has supported WebP since Windows 10 1809.
In what capacity? Because the Photos app does not. Hence ‘barely’. Also HEIC support is globally shit. Apple can eat a dick.
In what capacity?
The built-in APIs for handling images (GDI+) added WebP support in 1809. This is mentioned in the the documentation for the drawing library in C#/.NET, which is a wrapper around GDI+: https://learn.microsoft.com/en-us/dotnet/api/system.drawing.imaging.imageformat.webp?view=net-8.0
I haven’t tried it in the Photos app recently, and don’t have a Windows system handy right now to try it out, but I know it works for sure in Paint, which uses GDI+ for image encoding/decoding (and thus supports all formats that Windows itself supports).
Of course, apps that use their own encoding/decoding code might have fewer features and support fewer formats than the native Windows code.
Edit: Apparently it works fine in the Photos app if you just change the extension? Which means Microsoft is doing something weird. The code to decode WebP must be there.
God I love the nerd shit on lemmy
The built-in APIs for handling images (GDI+) added WebP support in 1809.
The end user doesn’t work with Windows API. The end user works with web sites and apps, which are rarely native these days. And there you’re often limited to png/jpg for uploads.
most software supports it
Definitely not my experience
Chefs Kiss
