It’s probably more of a scale thing, going a conversation server side need CPU time, if it can be done prior to upload then server time is reduced. I think a lot of websites do client side processing so they can do more requests per server instance.
It would be wasteful to upload the full size image only to throw most of it away. JPEG compression is very cheap, especially at low resolutions (I assume that image search uses a pretty low-resolution source image). Doing it this way is actually what I would do for best user experience. (Not saying that they aren’t doing other malicious things, but doing the resizing on the client is actually a good idea)
LodeMike@lemmy.today 11 months ago
Yes because as we all know that’s too hard for Google to achieve.
Celestus@lemm.ee 11 months ago
LodeMike@lemmy.today 11 months ago
Yes because as we all know 100% of browsers have a canvas.
lime@feddit.nu 11 months ago
which ones don’t?
also, good goalpost moving.
purplemonkeymad@programming.dev 11 months ago
It’s probably more of a scale thing, going a conversation server side need CPU time, if it can be done prior to upload then server time is reduced. I think a lot of websites do client side processing so they can do more requests per server instance.
kevincox@lemmy.ml 11 months ago
It would be wasteful to upload the full size image only to throw most of it away. JPEG compression is very cheap, especially at low resolutions (I assume that image search uses a pretty low-resolution source image). Doing it this way is actually what I would do for best user experience. (Not saying that they aren’t doing other malicious things, but doing the resizing on the client is actually a good idea)