cross-posted from: https://lemmy.blahaj.zone/post/16648244
efficient game design rule
When you trigger an error in a loop but tell your code to not crash but keep logging
this post was submitted on 19 Sep 2024
260 points (94.8% liked)
Microblog Memes
5726 readers
1402 users here now
A place to share screenshots of Microblog posts, whether from Mastodon, tumblr, ~~Twitter~~ X, KBin, Threads or elsewhere.
Created as an evolution of White People Twitter and other tweet-capture subreddits.
Rules:
- Please put at least one word relevant to the post in the post title.
- Be nice.
- No advertising, brand promotion or guerilla marketing.
- Posters are encouraged to link to the toot or tweet etc in the description of posts.
Related communities:
founded 1 year ago
MODERATORS
This seems like an extreme reaction.
"it's a text document"?? It's meant to be read. What else is it supposed to be?
Looking at you, journald 😒
making a logging system that saves logs as surrealist artworks.
"the warbled edges and polygonal artifacting of the apple in front the Man's face suggests the crash was due to floating point imprecision"
The crash logs need to be saved as brainwaves, and dreamt about while the lead dev is asleep.
I'm not disagreeing that the game dev is irresponsible, but NTFS compression would've done wonders on that huge, easily compressible text file.
or … you know … logrotate exists. but i guess the extra few kB from including a logrotate binary would have been bloat.
The fact that it has a log extension doesn't necessarily imply that it's a text file.