An extension is a suffix that provides information to a user about the nature of a file without the need for additional interaction. My scripts are all suffixed with “.sh”. And their backups as “.sh.bak”. And sorting and finding are a breeze. And suffixless entries are easy to identify as directories. File symlinks get a prefix.
On Windows you can also have text files with config specific to some software. They may have no or a generic extension, and you can edit them the same in a text editor or a hex editor. There are varieties of text with script/markup/settings that you couldn't reliably detect without some context. The computer would have to do a lot of number crunching to determine that it is only ASCII text and not followed by some other data. There are format identifiers that try to make that guess on Windows. You wouldn't run them on a few hundred files in a list. Does Linux have a file manager that sends .jpg to a graphics editor, and .txt to a text editor? If it only does generic things like "move" then he doesn't need to care about the contents, and it works the same on Windows. I've recently noticed that there is an army of file extensions for Linux graphics formats: PBM, PPM, PGM, PFM, PNM, PAM. Every color depth gets is own extension. That is weird. On Windows, you'd just get, let's say TGA, and it then reads the data to determine the subtype.
Important i think meaning the file itself changes behaviour Its the interpreters that change context by looking at the extension. You could Call the file .batman and Its contents would not be affected
Full Playlist - ruclips.net/video/__iKSnQXe_o/видео.html
An extension is a suffix that provides information to a user about the nature of a file without the need for additional interaction.
My scripts are all suffixed with “.sh”. And their backups as “.sh.bak”. And sorting and finding are a breeze. And suffixless entries are easy to identify as directories. File symlinks get a prefix.
On Windows you can also have text files with config specific to some software. They may have no or a generic extension, and you can edit them the same in a text editor or a hex editor. There are varieties of text with script/markup/settings that you couldn't reliably detect without some context.
The computer would have to do a lot of number crunching to determine that it is only ASCII text and not followed by some other data. There are format identifiers that try to make that guess on Windows. You wouldn't run them on a few hundred files in a list.
Does Linux have a file manager that sends .jpg to a graphics editor, and .txt to a text editor? If it only does generic things like "move" then he doesn't need to care about the contents, and it works the same on Windows.
I've recently noticed that there is an army of file extensions for Linux graphics formats: PBM, PPM, PGM, PFM, PNM, PAM. Every color depth gets is own extension. That is weird. On Windows, you'd just get, let's say TGA, and it then reads the data to determine the subtype.
Always waiting for ur explanations 💐
Getting close to the halfway mark to 1 million subs 👍
Is should make a function that wont start a file if the extension is not equal to the filetype. And would warn me.
good info. thanks!
I feel like the extension is pretty relevant considering every time you changed it the output changed
Important i think meaning the file itself changes behaviour
Its the interpreters that change context by looking at the extension. You could Call the file .batman and Its contents would not be affected