Or a renamed txt. Eg, .js, .py, .css, .html, .json
Thank God they went with file name extensions so we didn’t have to preface every source .txt file with header content to instruct the editor about what kind of content it would have.
Why do I need to put that at the start of bash, desktop, and html files then?
Because both ways are used. Microsoft relies on file names, linux on the first bytes of the file.
Nothing unless you want to serve them without some other way to see what file type they are.
You can run bash scripts with bash.
Don’t know what a desktop file is.
HTML has that because webservers used to not have auto media type detection and response headers.
AKA “Why zip doesn’t compress things much any more”.
I see images, audio, or video files distributed in zips far too often. You’re getting maybe a percent of compression if you’re lucky; just distribute the raw files or use a non-compressed bundle format like tar.
Zipping a file repeatedly typically doesn’t reduce the size further after the first time.
Not sure what the original point was but curiously I happened to use file on a an Apple .numbers file recently and found that it was a .zip file in disguise with zero compression.
So maybe the point was that it’s used often as a container format more often than it’s used for compression? Just my (unrelated) general computer work would also suggest this.
Your MOM is a renamed zip!
And if not, wow, she really kept herself in shape. Very good.
Counterpoint: what?
Not really. The “file types” you’re talking about are expected to contain whatever things in a very specific format.
You’re really just saying “many file types use an efficient and common compression algorithm”. Which is correct, obvious, and to be expected.
What happens if I put an mp3 or an epub file in there with the xml? Is it still a word document?
Maybe, I was just giving an example. Like Java jar files are just zip files with other jars in them.
