Man THIS is what the Internet was all about
The next one contained a Flintstones rule 34 image, which I won’t include here for obvious reasons.
;-;
So how does the heavier-when-inflated bowling pin man work? Does it thrust downwards somehow?
Likely answer —we’re being nerds and reading too much into it.
No—
—3 lbs of thrust isn’t going to be happening, speaking from experience with model planes.
—3lbs of the air inside is compressed and weighs more is even farther from possible.Likely—
—It only has the battery, fan, whatever when it’s running, and they don’t count that when it’s uninflated for some reason. Like how cars have dry weight, curb weight, and gvrw.
—somewhere in the spec sheets, someone made a mistake, two people worked on things and rounded differently, some other clerical/communicative error.It could also be just what it “feels like”, based on the measurement method of “made it the fuck up”.
So how does the heavier-when-inflated bowling pin man work?
Usually from 9 to 5.
Imagine having the time to just do this. Lol I imagine I’d do the same thing, actually.
The nostalgia is strong in this one, I love these discoveries.
How do these contain random files like this? Isn’t it just a file that applies some kind of visual effect to the media player?
They’re zip files, with the extension renamed. So you could probably have almost anything in one.
Oh so they’re actually created the same way as a zip file? That makes sense I guess. Thanks.
It is literally a zip file. If I remember correctly you have to write some xml which describes the layout of the skin and then include any images you need, you then zip it and change the file extension to wsz. So really you could put anything in a skin.
This is a common design pattern for “packages”.
Winamp uses a pattern called package management for its skins. Same as chrome extensions, etc etc. Most of the time we don’t call it that because the term is more reserved for package sets which provide a wider array of functionality. The iOS app store is a package management system.
The packages, much like boxes being handled by FedEx, contain standardized elements which allow that package management system to find and install the package. Much like how when you ship a box through FedEx the first thing they do is put standardized labels on that contain all the different barcodes that different parts of their process use to route the package.
Like with Chrome extensions, there are certain files that must be there (iirc something like a manifest.json file) and others which can be anything. If you need an image for a button, that image becomes part of the package. If you need a complex set of rules then maybe there’s a little sqlite file or csv file containing all the rules. Or font files, or whatever.
Thing is, the package format is defined by the “box” as opposed to by the “contents of the box”.
Just to put this in context:
There’s only so many ways to turn a bunch of files into one - mainly, you stick them back to back. Easy.
Then, there’s an infinite ways to compress that file… You could come up with you own method, but what good is that? It’s better and smarter to use a format already supported by your users
So of course most bundles are the same archive type under the hood. Everything from backups to installers - you shouldn’t be inventing new formats without a damn good reason
The author touches on this near the beginning-
Winamp skins are actually just zip files with a different file extension
So they’re treating them like archives and extracting them
