Giver of skulls

Verified icon

  • 0 Posts
  • 287 Comments
Joined 102 years ago
Cake day: June 6th, 1923
  • Skull giver@popplesburger.hilciferous.nltoTechnology@beehaw.org•Portable Network Graphics (PNG) New Specification
    11·
    3 days ago

    PNGv4/v5 may improve compression but it won’t be backwards compatible. It’ll get stuck in the same kind of limbo JPEG-XL is. Until that gets resolved, we’ll have to stick with AVIF/HEIFF/WebP.

    I don’t really see the need for advanced compression in lossless files. You generally don’t download those in bulk without looking at lower quality previews anyway. Would be nice if the real file supports the same colour space the preview file does anyway. I’ll appreciate it when it lands, but I don’t think I’ll spend the hours converting my photo library to save maybe half a gigabyte of space.

  • Skull giver@popplesburger.hilciferous.nltoTechnology@beehaw.org•Portable Network Graphics (PNG) New Specification
    12·
    3 days ago

    What a weird take. Alpha channels are used all the time. A lot of tools use WebP for them, though. Things like stickers and emoji in chat apps often recode into WebP or force you to figure out how to make a WebP with a certain configuration to accept your pack, but from there on out they rely on alpha channels.

    MacOS app icons are a collection of layers with alpha channels embedded into them, stacked on top of each other, or themed individually. Unless you’re blind, any iOS or macOS user encounters alpha channels every time they turn on their screen. On Android, those files are even actual PNGs. On Windows, those are .ico resources, and everything larger than 64x64 is guaranteed to be a PNG embedded inside of an .ico (possibly embedded inside of a .exe/.dll/etc.

    WebP has replaced jpeg for most web content already when it comes to compression. This just solves things like “how do I save my HDR images without degrading them every time I hit save”.

  • Skull giver@popplesburger.hilciferous.nltoProgrammer Humor@lemmy.ml•My favorite part of the job
    11·
    14 days ago

    Country codes are variable. Even the “I’m about to dial another country prefix” (usually + resolves to 00 but that depends on country and carrier) is variable. Phone number lengths are variable. Phone numbers are often written in non-Arabic numerals. Phone numbers can have specific digits in the middle of the number to reroute the call to another carrier.

    You can try to parse phone numbers if you’re writing a specific phone number parsing library, but you’ll need to keep up with the ITU documents, the numbering plans of all countries and satellite providers, and provide support for older standards going back to the 60s. You’ll need to deal with edge cases that your language probably doesn’t even have names for. And most importantly, you’ll have to guess what country the phone number is from based on context clues such as the user’s language or location or locale because phone numbers can be and are reused across borders.

    Phone numbers are worse than time zones. Don’t parse them yourself unless you’re building an international phone interconnect.