Skip to content
DevMeme
4940 of 7590
DataFormats Post #5407 · source on Telegram

A Supabase Tweet on a JPG-less Utopia

Description

This meme is a screenshot of a tweet from the company Supabase. The text of the tweet reads, 'society if jpg was never invented'. Below the text is an image depicting a gleaming, futuristic, utopian city with sleek, modern architecture, flying vehicles, and green park spaces. The visual humor and irony come from the fact that the image itself is heavily stylized to look like ASCII art or as if it has been passed through a strong edge-detection filter. This creates a highly artifacted, low-fidelity rendering of the supposed high-tech utopia. The joke is multi-layered: it plays on the common developer complaint about the lossy compression artifacts of the JPG format, while ironically presenting the 'better' world in a format that is itself visually degraded and inefficient, mocking the idea that a single technology is the root of all problems

Comments

7
Anonymous ★ Top Pick Society without JPGs would be a utopia, not because of higher image fidelity, but because we'd finally have enough storage and bandwidth from not saving petabytes of JPEGs to run our ASCII-art-rendered cities
  1. Anonymous ★ Top Pick

    Society without JPGs would be a utopia, not because of higher image fidelity, but because we'd finally have enough storage and bandwidth from not saving petabytes of JPEGs to run our ASCII-art-rendered cities

  2. Anonymous

    Proof that if you ban JPEG but keep the 100 KB perf budget, someone will just reinvent lossy compression and we’ll all end up living inside 8×8 DCT blocks anyway

  3. Anonymous

    Without JPEG we'd still be arguing whether BMP or TIFF should be the web standard while our CDN bills approach the GDP of small nations

  4. Anonymous

    Ah yes, the classic paradox: complaining about JPG compression artifacts using an image so heavily compressed it looks like it was saved at quality level 5 through a chain of seventeen Discord uploads. It's the visual equivalent of writing 'TODO: refactor this' in production code that's been running for five years - we all know what should happen, but here we are, living with the consequences of choosing file size over fidelity since 1992

  5. Anonymous

    Without JPEG’s DCT and 4:2:0, every homepage hero becomes a 12MB PNG and the postmortem reads: egress budget exhausted, contributing factor - marketing uploaded a bitmap

  6. Anonymous

    If JPEG hadn’t normalized DCT and 4:2:0, marketing would ship 8K lossless PNG hero banners - the CDN bill would dwarf the database, and our performance OKR would be “raise Series B.”

  7. Anonymous

    JPEG: where you pick quality=90 to halve file size, but inherit eternal block artifacts haunting your A/B tests

Use J and K for navigation