5 ms·
I think that: a) Google should be doing that in a memory safe language, kinda nuts that they haven't started doing that already b) Apple could definitely writ
by insanitybit 3y ago
I think that:
a) Google should be doing that in a memory safe language, kinda nuts that they haven't started doing that already
b) Apple could definitely write their own? Unless I'm missing something crazy here, it seems like they could burn 8 figures and just have their own implementations that are safe
- astrange 3y agoIf you reimplemented it they'd just change it. It's Google, they can't stop themselves.
- insanitybit 3y agoI don't believe you, frankly. I don't believe that Google makes breaking changes to existing image formats often.
- astrange 3y agoThey already did - WebP added a lossless mode and VP8 was updated to VP9. Though the same may happen to JPEG; it always had 10-bit and 12-bit modes but most decoders don't support them. (Not sure if they can decode it as 8-bit or not.)
- insanitybit 3y agoAre those breaking changes? I'd assume that a decoder would continue to work, just would not support the lossless mode/ VP9.
- astrange 3y agoIt will work on old files (since they've already been encoded) but not on new files with the same file extension, and not on, say, YouTube.
- insanitybit 3y agoInteresting, thanks.