News for hackers. Stuff that matters.

A comment on How Discord Resizes 150M Images Every Day with Go and C++. Parent comment

Re:How Discord Resizes 150M Images Every Day with Go and C++ by mark-r on Tuesday November 14, 2017 @01:01PM (#15697487)
There's no reason this couldn't be a two-step process, resizing to something reasonable on the client then fine-tuning it on the server. I'm presuming you don't see the need to start with multi-megapixel images.
[ Parent | on HN ]
Re:How Discord Resizes 150M Images Every Day with Go and C++ by wastedhours on Tuesday November 14, 2017 @01:21PM (#15697691)
> I'm presuming you don't see the need to start with multi-megapixel images.

Might be a fair presumption today, but might not be for the future with hiDPI screens, VR etc... for the relative storage costs, it'd be better to have the original, and then you can programmatically run from there.

[ Parent | on HN ]
Re:How Discord Resizes 150M Images Every Day with Go and C++ by mark-r on Tuesday November 14, 2017 @01:33PM (#15697812)
Today's hiDPI screens can already display more detail than your eye can perceive. The issue wasn't about storage costs, it was about transmission costs which still matter for the foreseeable future.
[ Parent | on HN ]
Re:How Discord Resizes 150M Images Every Day with Go and C++ by dboreham on Tuesday November 14, 2017 @05:07PM (#15699653)
Perhaps, but I think you can compress current-day phone images considerably without losing any actual image fidelity (because the sensor pitch significantly exceeds the lens resolution, and .. noise).
[ Parent | on HN ]