"I'm tired of these stupid image file formats, so I'm contributing to the problem"

wow, coverting a binary -> string -> do string manipulation -> show from the string. What's inside your head bro, it's pure genius

By converting it into hex of 6 characters, you lost transparency. However, if you made it hex of 8 characters long, you could keept the transparency.

The major difference between jpeg and PNG is not only transparency but also the compression

web✅code editor✅programing lang✅text editor✅image file format✅operating system❌

why store the hex as a literal string, a byte can be represented in one character (byte), instead you use two bytes to represent one byte??

why is this video interlaced

Tip: you can half the size of your files if you store the RGB values as raw bytes instead of characters. Each character is 1 byte long (assuming you are using a 1 byte character encoding like ASCII or UTF-8), but a hex character just represents half a byte in a human readable format. "9e", for instance, just represents the number 158 (uint8) which only takes up one byte, where storing "9e" as two characters you are using two bytes. Hex goes from 00 (0) -> FF (255), which is exactly how much a byte can hold. To do this you'll need to allocate a buffer of the number of pixels in the image times 3 (RGB per pixel = 3 bytes (1 byte for each colour) * number of pixels), then for each pixel: write a uint8 for the red value, write a uint8 for the green value, write a uint8 for the blue value. To read the file, loop over each pixel and read each byte (uint8) instead of writing.

why this video is 1080i?

Why is your video interlaced

2:27

bro made a .bmp

Now make a .huh file that is an audio format

wowzers, im converting all images in my gallery to .bruh files! so efficient, fast and lightweight

avif is actually conceptually really cool:

i wanted to make a JSON image format

So this is what it feels like to be the guy who made the .webp file format

the interlacing on this video is making me crazy

1:21

"Hex" is representing the color data in base sixteen whilst "RGB" (don't include the alpha channel, it's not a fair comparison) is representing it in base 10. It's the same exact data. There's no space "reduction" if you don't bloat it by storing it in ASCII, but you figured that out.