this post was submitted on 13 Sep 2023
683 points (97.6% liked)

Programmer Humor

32472 readers
880 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[โ€“] observantTrapezium@lemmy.ca 40 points 1 year ago (1 children)

Nothing wrong with that... Most people don't need to reinvent the wheel, and choosing a filename extension meaningful to the particular use case is better then leaving it as .zip or .db or whatever.

[โ€“] CoderKat@lemm.ee 5 points 1 year ago

Totally depends on what the use case is. The biggest problem is that you basically always have to compress and uncompress the file when transferring it. It makes for a good storage format, but a bad format for passing around in ways that need to be constantly read and written.

Plus often we're talking plain text files being zipped and those plain text formats need to be parsed as well. I've written code for systems where we had to do annoying migrations because the serialized format is just so inefficient that it adds up eventually.