this shows perfectly how much fauna hates to be wrong. When a clip is 7 min and all she does is try to convince us that is Wahve and not wave. She got my respect for the commitment.
I too agree with the WHAV pronunciation. I was hoping before clicking on the video that she pronounced it the CORRECT WAY, and she does. The check-checkmate at the end with mentioning flac file format was just icing on the cake, glorious.
Fun fact: Windows only allowed for 3 character file extensions back in the day and that's pretty much why. Although it's been many years since that limit was yeeted, people just kinda do it even if it doesn't necessarily make sense.
Yes, though the 3 character extension coasted a long way on fumes after 95 was out. I feel like Office’s upgraded XML-based file formats were the first time I can remember Microsoft using 4 character extensions (.docx instead of .doc for Word, for example) and it seemed weird to me at the time!
It still kinda makes sense if you wanna maximize compatibility: some poorly coded software/devices might accidentally not support file extensions above 3 characters, so sticking to that limit might avoid some issues later.
MSDOS's FAT file system only allowed an 8.3 filename. The modern NTFS is what allowed longer path names. It had alot of other advantages. IIRC it started being used in Windows NT, that was the SERIOUS BUSINESS OS system. Mainstream users would start using Windows 95 in.. Windows 95. Before Windows 95 you wouldn't really consider Windows 3.11 it would be very foreign to modern users.
The full name if a file type doesn't matter for how you pronounce the acronym. I believe wahv is how it was called back in the day. No one pronounces acronyms folowing english patterns, especially when English is insanely inconsistent.
filename extension format using anything descriptive helps, like abbreviation or initialism too. It can become it's own word but it's easier when it's already a word. Taking the abbreviated .bin files for binary files. Ya say 'been files' even tho it's bi-nary. Then ya troll and tell somebody all the .bin files belong in the trash/recycle bin so they delete them all. lol I've heard it was called the wastebasket too? I dunno.
It’s pretty easy to disprove the argument that acronyms always follow the pronunciation of the words that make it up. The example I always think of is that it would be like trying to argue that SCUBA should be pronounced “SC-UH-BA” cause the “U” stands for “underwater” lol
While you are correct no file format types are acronyms they are initialisms or abbreviations and in this case in abbreviation. You either say the letters(MP3, PDF, PSD, ISO, GIF, PNG) or you say the name/abbreviations of the file format(BIN, TXT, EXE, ZIP, DOC) everything else is a colloquialism so it doesn't matter. Which is kind of your point on acronyms.
Filesystem table format. Like how books are labelled at the library, 8.3 format (11 characters) was largely enough when files were treated like a bookshelf. When computers started being used by non-doctorate scientists, and software started using hundreds of files, it became clear that the old library system was outdated, so the LongFileName was created. It kept the short 8.3 names, but created an additional "file" next to the real one, hidden to the user, that stored the longer names. If the Operating System had LFN support, it would read these hidden files and display the longer names in the User Interface, as if the file was really named that way in the filesystem. A few troubles would happen when an old DOS program, or when booting in DOS mode, would rename the files: the LFN hidden files wouldn't be changed by the DOS program, so next time a LFN OS would try to read the LFN files, it would simply skip the incorrect entries, leaving the affected files with their short 8.3 names. That's why you may have encountered files suddenly named in uppercase "PROJE~1.DOC" on a faulty USB key. When facing corrupted LFN entries, Windows automatically create new entries, by keeping the first 6 letters of the 8.3 name, adding ~ and a number, then a 3 character extension. That way the files can still: - be accessed in the file explorer - be opened by the right software (if the original extension is longer, you still got the first 3 characters!) - and the files do not collide (same name)(if needed, basename is shortened to even less characters to add two numbers after the ~) NTFS natively supports long filenames and can work without any 8.3 names, so in theory ever since Windows XP we could be working with longer filenames. With emojis. Emoji file extensions. Like this: 👉👈.🥺 Or this: ☝️.🤓 However a lot of OS still create a 8.3 name + a LFN addon to keep legacy compatibility - because a LOT of software still rely on 8.3 filenames, as it's much easier to only deal with ASCII (8.3 format) rather than upgrading and keeping up with all the modern OS Unicode implementation (LFN format). The 8.3 filename system is a small security risk, and a possible source of performance issues, but it is more than likely that most of your devices are still relying on it, only using tricks to display a longer name to you. For example, last time I checked, Windows 10 had 8.3 filenames turned on by default (at least for the C: drive). So the _FaunaSweep.wav_ you use as a startup sound? It's still named FAUNAS~1.WAV under the hood 🌱
Ah, I remember listening to this live. I usually don't chat much in Fauna streams, as I like just listening to her in the background, but this part pulled me into the chat. I especially laughed at Fauna Lossless Audio Content. I want me some of that.
@@SolaireIntensifies No, but since English loves to make exceptions for their rules (sometimes they even have exceptions for exceptions to the rules) Fauna is wrong either
@@seneca983 How should the OS know how to interpret the random jungle of bytes in the file then? If it was arbitrary, you couldn't know if the numbers you are reading from disk are text, an encoded video, or encoded sound.
@@kukuc96 It's up to applications to interpret the bytes. Of course, the OS can choose a default program to open each file based on what is at the end of the filename. What you're talking about is orthogonal to the issue of allowing arbitrary filenames. Even in an OS that enforces e.g. the 8.3 character filename format you can still name the files incorrectly (e.g. name an MP3 file as TXT) and the OS probably can't recognize what would be the correct application to use. It's generally good to follow conventions in naming files but that's not a reason for the OS to not allow names like "a.b.cdefghijk".
I’m one of those weirdos that knows it means “waveform audio format” but decides to pronounce it “Wahve” because it just feels wrong from a language perspective to pronounce it “wave” with that “e” missing.
the E at the end of the word changes the "ah" sound to a "ay" sound this is how E's at the end of words function mostly so it makes sense for Wav to be pronounced Wahve not Wayve cos there is no E to alter the vowel
The thing is .wav is .wave are now mime types of each other. You use one of the other it will be read the same by the computer. For example .jpg and .jpeg are read the same way by the computer.
Wikipedia says it has both readings: "Waveform Audio File Format (WAVE, or WAV due to its filename extension pronounced "wave" or "wæv")" Yes, it stands for "waveform" - but the file extentions are not an acronyms per-se, and can be confusing if read in "full form". TXT extension stands for Text. Yet you would not really want to say it as "text file" - but rather as "ti-ex-ti file". So it makes more sense to read any extentions as distinctively as possible. I also do read it as "waw" all the time. And GIF should be "gif" only (like in "golf"). Because there also exists an unrelated JIF extension. Used for older versions of JPEG images - stands for "JPEG Interchangeable Format", as described in Annex B of JPEG standard.
I used to call it wav until about 200? then somewhere i just dropped it called it and started calling it wave... Hmm, well it happens! if i remember i actually used to call a 'dot wav' because it would sound weird if i would say wav on its on
I actually looked it up and turns out it is pronounced "wave"! I remember making a lot of WAV files for HLDJ ages ago and always called them "wahv"-files too...
It's becoming more clear that the 3 generations of internet users( GenX, Millenials, and Zoomers/with some "Zillenial" thrown into the mix) are creating mis translations and mis communications between each other. WAV vs Wave, Sped up vs Nightcore, Thick vs T H I C C. Were having sub groups being build ontop of other sub groups without even knowing it.
She is "more" right and chat is wrong. It is "Waveform Audio File Format" and it IS "microsoft.waveform-audio". She is 100% correct it is a Microsoft audio file that could only be used on windows and linx till recently. It also is a .WAVE extension as well. All file types are initialism or abbreviations so if you want to be technically correct then you say each letter or you say the full file name. Think .PDF .EXE .TXT .MP3 .WAV .PSD .RAR .ISO etc. if you say any of them as words such as "gif" then you are saying a colloquialism and that can't be wrong. This is another prime example of chat gaslighting super hard probably unintentionally.
The little icon that appears for a website in a tab is a favicon, a FAHVicon. Fav is also FAHV, because you’re just misspelling FAVE. I clicked this wanting to tease her but she convinced me!
For those wondering; It stands for Waveform Audio File Format, it's header contains WAVE, and the Internet Media Type is audio/wave. However due to file extension limitations on early Windows it got the .wav extension and a file header with WAV or Internet Media Type with audio/wav is also valid. But I'd like to think this is clear enough evidence that it should be considered to be wave and not wæv Small edit: I had paused the video literally a few seconds before chat mentions "Waveform" xD Additional comments based on me finishing the video; WAVE was actually developed by both IBM and Microsoft, so it was definitely made with Windows in mind (though many files are since most non-server machines run Windows). The 3 characters for file extensions came from the fact that computers used to have much greater limitations including total file name length. And the fact that some file systems used the extension as part of the meta-data. So a 6+3 scheme (only upper case) emerged on many systems (though there existed other scemes as similar as 6+2 and as different as where files actually got 2 names). Which, when it was considered too small, lend itself to a 8+3 scheme; just enough extra to be useful while still easy to implement. But with Windows 95 (and a specific version of Windows NT), in oder to improve the user experience, the SFN (short filename) was abandoned and with NTFS (NT File System) file extensions could be as long as you had remaining characters for the total character limit. WAVE was developed in 1991 (well before Windows 95 and NTFS), whereas FLAC (Free Lossless Audio Codec) was developed in 2001, hence why it does have a 4 letter extension and WAVE does not. Since many file systems, even back then, used things like file headers in combination with the filename and extention to determine what the actual content of the file was, not only could you name your file 1992_02_22_myrecording.wave, you could also just name it README.txt (though fun fact, my linux machine automatically thinks any readme.extention file has the file type "README file" and will try to open it with a text editor first) and it can still be played in a media player. So yes "NOW we can" As for how things should be spelled... I'd like to remind all English speakers we pronounce "knife" as ˈnaɪf.
Look ma, I’m in an SJTree clip!
Legit though this whole bit had me rolling on the floor, so kudos to you for clipping it. Absolute Fauna gold.
I love how fauna's topics can end up in more obscure technical things and she can keep up with the convo. It really makes her unique
this shows perfectly how much fauna hates to be wrong. When a clip is 7 min and all she does is try to convince us that is Wahve and not wave. She got my respect for the commitment.
#justgamerkirinthings
ngl i always said wave but i assumed it was supposed to be wahv
She did say one time she used to be that one person who corrects someone on their grammar.
Couldn't it just be her milking these moments for engagement and banter?
Why would it be spelled WAV and not be pronounced wav? This is the gif situation all over again.
I've always pronounced it was wahv to not get it confused with wave
me too
I agree with Fauna here. It needs the e to be pronunced as wave. If you shorten favorite into fav, I'll say it as fahv.
@@iwansays she's my fav.
@@sawyersimpkins9428 favna?
Fauna's minecraft mondays are a great companion during work, you get a sense of peace even if Fauna malds.
I really don't know why but All those random things in the stream just make us more love Fauna
She gives off friendly babysitter vibes.
Hmmmm how friendly are we talking about?
Bow chica bow wow.
so saplings are babies
"Tell that to my *fav* vtuber" was fucking world-shattering
I too agree with the WHAV pronunciation. I was hoping before clicking on the video that she pronounced it the CORRECT WAY, and she does. The check-checkmate at the end with mentioning flac file format was just icing on the cake, glorious.
Man... I would give my lifespan just to have a FLAC (Fauna lossless audio content) session even for just a couple of seconds
This is straight up a Northernlion like bit
Fun fact: Windows only allowed for 3 character file extensions back in the day and that's pretty much why. Although it's been many years since that limit was yeeted, people just kinda do it even if it doesn't necessarily make sense.
Yeah cause i was thinking about jpeg
It's more due to DOS and its short file names. Windows 95 introduced long file names
Yes, though the 3 character extension coasted a long way on fumes after 95 was out. I feel like Office’s upgraded XML-based file formats were the first time I can remember Microsoft using 4 character extensions (.docx instead of .doc for Word, for example) and it seemed weird to me at the time!
It still kinda makes sense if you wanna maximize compatibility: some poorly coded software/devices might accidentally not support file extensions above 3 characters, so sticking to that limit might avoid some issues later.
MSDOS's FAT file system only allowed an 8.3 filename. The modern NTFS is what allowed longer path names. It had alot of other advantages. IIRC it started being used in Windows NT, that was the SERIOUS BUSINESS OS system. Mainstream users would start using Windows 95 in.. Windows 95. Before Windows 95 you wouldn't really consider Windows 3.11 it would be very foreign to modern users.
I am now pronouncing MOV as ‘MAW-ve’ as god intended.
how tf were you pronouncing it before Move?
"Mohv"
@@-hello6177 Well, Move, honestly. I'm just making a funny.
i once heard someone call it a 'move' file and i had a minor inner crisis about how long i've been mispronouncing it bc i fuckin say 'mawve' too
M-O-V
"WAV = Windows Audio Something that starts with a V". Ceres Fauna Ch. Hololive-English May 2023 (funniest shit i have ever seen)
it's waveform audio format, but you can call it either wav or wave
@@keepcalmandholdspace Tidal Wave
I love her so much 😭
This is what I will present if I am ever asked why I watch Fauna. I find it to be apt.
I really enjoyed watching this discussion live. Thanks for clipping it!
And I'm on the same side as Fauna lol. I also pronounce it as WAHve
Fauna.lmao
The full name if a file type doesn't matter for how you pronounce the acronym. I believe wahv is how it was called back in the day. No one pronounces acronyms folowing english patterns, especially when English is insanely inconsistent.
filename extension format using anything descriptive helps, like abbreviation or initialism too. It can become it's own word but it's easier when it's already a word. Taking the abbreviated .bin files for binary files. Ya say 'been files' even tho it's bi-nary.
Then ya troll and tell somebody all the .bin files belong in the trash/recycle bin so they delete them all. lol
I've heard it was called the wastebasket too? I dunno.
It’s pretty easy to disprove the argument that acronyms always follow the pronunciation of the words that make it up. The example I always think of is that it would be like trying to argue that SCUBA should be pronounced “SC-UH-BA” cause the “U” stands for “underwater” lol
@@AeolusAspect There's tons of examples. Nasa isn't pronounced Nesa. Jpeg isn't Jfeg, etc. Idk why people get so weird about file types lol
While you are correct no file format types are acronyms they are initialisms or abbreviations and in this case in abbreviation. You either say the letters(MP3, PDF, PSD, ISO, GIF, PNG) or you say the name/abbreviations of the file format(BIN, TXT, EXE, ZIP, DOC) everything else is a colloquialism so it doesn't matter. Which is kind of your point on acronyms.
Am old, in the 90s we said wave.
3:40 from what i remember they only had 3 letters to work with back then right? So wave becomes dot wav for the extensions format.
Filesystem table format.
Like how books are labelled at the library, 8.3 format (11 characters) was largely enough when files were treated like a bookshelf.
When computers started being used by non-doctorate scientists, and software started using hundreds of files, it became clear that the old library system was outdated, so the LongFileName was created.
It kept the short 8.3 names, but created an additional "file" next to the real one, hidden to the user, that stored the longer names.
If the Operating System had LFN support, it would read these hidden files and display the longer names in the User Interface, as if the file was really named that way in the filesystem.
A few troubles would happen when an old DOS program, or when booting in DOS mode, would rename the files: the LFN hidden files wouldn't be changed by the DOS program, so next time a LFN OS would try to read the LFN files, it would simply skip the incorrect entries, leaving the affected files with their short 8.3 names.
That's why you may have encountered files suddenly named in uppercase "PROJE~1.DOC" on a faulty USB key. When facing corrupted LFN entries, Windows automatically create new entries, by keeping the first 6 letters of the 8.3 name, adding ~ and a number, then a 3 character extension.
That way the files can still:
- be accessed in the file explorer
- be opened by the right software (if the original extension is longer, you still got the first 3 characters!)
- and the files do not collide (same name)(if needed, basename is shortened to even less characters to add two numbers after the ~)
NTFS natively supports long filenames and can work without any 8.3 names, so in theory ever since Windows XP we could be working with longer filenames. With emojis. Emoji file extensions. Like this: 👉👈.🥺 Or this: ☝️.🤓
However a lot of OS still create a 8.3 name + a LFN addon to keep legacy compatibility - because a LOT of software still rely on 8.3 filenames, as it's much easier to only deal with ASCII (8.3 format) rather than upgrading and keeping up with all the modern OS Unicode implementation (LFN format).
The 8.3 filename system is a small security risk, and a possible source of performance issues, but it is more than likely that most of your devices are still relying on it, only using tricks to display a longer name to you.
For example, last time I checked, Windows 10 had 8.3 filenames turned on by default (at least for the C: drive).
So the _FaunaSweep.wav_ you use as a startup sound? It's still named FAUNAS~1.WAV under the hood 🌱
so many blessed giggles
I knew it was waveform, but I've always called it wahve
This led me down a road watching all her shorts. Her most recent one is cool. A UNIVERSE ALONE.
Ah, I remember listening to this live. I usually don't chat much in Fauna streams, as I like just listening to her in the background, but this part pulled me into the chat. I especially laughed at Fauna Lossless Audio Content. I want me some of that.
I've always said it like that. It makes sense if you don't know it's short for an actual word.
I don't care if she's objectively wrong, I also pronounced it like she did, therefore she has always been correct (not cope😎)
you can't be objectively wrong it's colloquialism so you're correct no matter which way you pronounce it.
Preach brother
Wahv gang
Objectively wrong to follow the rules of the english language? Fuck no.
@@SolaireIntensifies No, but since English loves to make exceptions for their rules (sometimes they even have exceptions for exceptions to the rules) Fauna is wrong either
As for 4 letter file extensions, I raise you: docx, xlsx, pptx, and all the other Microsoft office formats.
Let's not forget .torrent
They've been popping up like crazy for a while now, at this point naming them is just a pointless exercise
In a reasonable OS the dot and the extension are just a part of the files name and they can be arbitrary or absent.
@@seneca983 How should the OS know how to interpret the random jungle of bytes in the file then? If it was arbitrary, you couldn't know if the numbers you are reading from disk are text, an encoded video, or encoded sound.
@@kukuc96 It's up to applications to interpret the bytes. Of course, the OS can choose a default program to open each file based on what is at the end of the filename. What you're talking about is orthogonal to the issue of allowing arbitrary filenames. Even in an OS that enforces e.g. the 8.3 character filename format you can still name the files incorrectly (e.g. name an MP3 file as TXT) and the OS probably can't recognize what would be the correct application to use. It's generally good to follow conventions in naming files but that's not a reason for the OS to not allow names like "a.b.cdefghijk".
I had that short on loop, it was just so good lol
I’m one of those weirdos that knows it means “waveform audio format” but decides to pronounce it “Wahve” because it just feels wrong from a language perspective to pronounce it “wave” with that “e” missing.
The fact that she kept with the conversation made it so much fun.
I knew someone was gonna bring up "it has to be 3", when JPEG, FLAC, HTML, MIDI, etc have existed lol.
I can't bro, she's just too cute...
3:35 dang that tako (kirin version) so cute
Made by Ina herself and all of EN has them in their own chats
Blessed giggles cure my soul
mom get the camera I'm on sjtree's clip!
the E at the end of the word changes the "ah" sound to a "ay" sound this is how E's at the end of words function mostly so it makes sense for Wav to be pronounced Wahve not Wayve cos there is no E to alter the vowel
Fauna: 'Can I buy a vowel?'
One .WAV L, please!
The thing is .wav is .wave are now mime types of each other. You use one of the other it will be read the same by the computer.
For example .jpg and .jpeg are read the same way by the computer.
I'm devistated...
Now I just want to superchat EN mems to slip in subtle comments while slipping in ".wav" so we can sort out who pronounces it which way.
I sometimes wav to people on the street
For all the one tree hills to die on.
I agree. It's WAV not wave. Idc who says I'm wrong. I'm sticking to my guns on this one.
what a rollercoaster of emotions
Wikipedia says it has both readings:
"Waveform Audio File Format (WAVE, or WAV due to its filename extension pronounced "wave" or "wæv")"
Yes, it stands for "waveform" - but the file extentions are not an acronyms per-se, and can be confusing if read in "full form".
TXT extension stands for Text. Yet you would not really want to say it as "text file" - but rather as "ti-ex-ti file".
So it makes more sense to read any extentions as distinctively as possible. I also do read it as "waw" all the time.
And GIF should be "gif" only (like in "golf").
Because there also exists an unrelated JIF extension. Used for older versions of JPEG images - stands for "JPEG Interchangeable Format", as described in Annex B of JPEG standard.
Bruh fauna and I share the same brain cell, I've thought it was wahv and a windows format for like 10 years now
I want to see more computer nerd conversations.
I've NEVER heard anyone say it that way. I guess I'm not as old as I thought I was.
Never heard Wahve before. Fauna is a takodachi
the english wiki has been altered so fauna seems correct in pronounciation
Nigella Lawson once said: "Meecro-Wahvey"
Meecrowahve- Nigella Crimedaughter
Ngl I unironically always read "fav" as "fhav"
sound is wave remember that
In a way, this makes me want to push it further in the other direction and go from Wahve to Wawve
Well if nothing else I learned that day how to pronounce .wav because I made the same mistake
Tbf I always pronounced it Wahve, I never really thought about it.
Too good
I used to call it wav until about 200? then somewhere i just dropped it called it and started calling it wave...
Hmm, well it happens! if i remember i actually used to call a 'dot wav' because it would sound weird if i would say wav on its on
To be fair I also say "wahve" and "fahve" but that might be because my first language is french.
W.A.V for life
It's gif vs jiff all over aghein.
4:06 HTML and JPEG files: 🤨
I've never thought about pronouncing it like WAHV or WAAV before. 😂
gimme that windows audio vormat
Fauna is definitely right
Obviously the tako one
Nerdauna
damn now I can't unread FLAC as flake
It's .jif all over again
0:14 she's just like me fr fr
1:11 lmao the subs here
To be fair this is news to me I never knew how that was pronounced I honestly thought it was another GIF jif term
WAH
I actually looked it up and turns out it is pronounced "wave"!
I remember making a lot of WAV files for HLDJ ages ago and always called them "wahv"-files too...
It's becoming more clear that the 3 generations of internet users( GenX, Millenials, and Zoomers/with some "Zillenial" thrown into the mix) are creating mis translations and mis communications between each other. WAV vs Wave, Sped up vs Nightcore, Thick vs T H I C C. Were having sub groups being build ontop of other sub groups without even knowing it.
Oh Fauna 🤦♂️
She is "more" right and chat is wrong. It is "Waveform Audio File Format" and it IS "microsoft.waveform-audio". She is 100% correct it is a Microsoft audio file that could only be used on windows and linx till recently. It also is a .WAVE extension as well.
All file types are initialism or abbreviations so if you want to be technically correct then you say each letter or you say the full file name. Think .PDF .EXE .TXT .MP3 .WAV .PSD .RAR .ISO etc. if you say any of them as words such as "gif" then you are saying a colloquialism and that can't be wrong.
This is another prime example of chat gaslighting super hard probably unintentionally.
I'm afraid what she'll call a .wad file.
It's 'wade', because that's what you do when you're knee-deep in the dead.
It’s wahv. Yes it’s short for waveform, (waveform audio file) but it’s spelled wav so it’s pronounced wahv and that’s that.
Wave slave
Its pronounced "wave file" or "dot wahv" this is the only way
fauna cute.
personally, wayv or wahv or waahv or something else.
I also always said it Wahv, but with the knowledge that it was incorrect but funny
Flahva Flahv!
Lol
IMO it's a "dot wav" or it's a wave file.
wahvform
The little icon that appears for a website in a tab is a favicon, a FAHVicon. Fav is also FAHV, because you’re just misspelling FAVE.
I clicked this wanting to tease her but she convinced me!
Fauna correct as always, wahv just sounds right.
For those wondering;
It stands for Waveform Audio File Format, it's header contains WAVE, and the Internet Media Type is audio/wave.
However due to file extension limitations on early Windows it got the .wav extension and a file header with WAV or Internet Media Type with audio/wav is also valid.
But I'd like to think this is clear enough evidence that it should be considered to be wave and not wæv
Small edit: I had paused the video literally a few seconds before chat mentions "Waveform" xD
Additional comments based on me finishing the video;
WAVE was actually developed by both IBM and Microsoft, so it was definitely made with Windows in mind (though many files are since most non-server machines run Windows).
The 3 characters for file extensions came from the fact that computers used to have much greater limitations including total file name length. And the fact that some file systems used the extension as part of the meta-data. So a 6+3 scheme (only upper case) emerged on many systems (though there existed other scemes as similar as 6+2 and as different as where files actually got 2 names). Which, when it was considered too small, lend itself to a 8+3 scheme; just enough extra to be useful while still easy to implement.
But with Windows 95 (and a specific version of Windows NT), in oder to improve the user experience, the SFN (short filename) was abandoned and with NTFS (NT File System) file extensions could be as long as you had remaining characters for the total character limit.
WAVE was developed in 1991 (well before Windows 95 and NTFS), whereas FLAC (Free Lossless Audio Codec) was developed in 2001, hence why it does have a 4 letter extension and WAVE does not.
Since many file systems, even back then, used things like file headers in combination with the filename and extention to determine what the actual content of the file was, not only could you name your file 1992_02_22_myrecording.wave, you could also just name it README.txt (though fun fact, my linux machine automatically thinks any readme.extention file has the file type "README file" and will try to open it with a text editor first) and it can still be played in a media player. So yes "NOW we can"
As for how things should be spelled... I'd like to remind all English speakers we pronounce "knife" as ˈnaɪf.
I say WAV, because that is how it is spelt, and refuse to say a word how it isn't.
she's right tho
I agree with wahv
Ngl, tried paying attention but man, those giggles kept spiking my blood sugar
Wahve
Bo-womp
Always pronouced "wav" as "wave", but that "fav" comment made me question if that's correct, since I've always pronounced "fav" as "fahv"
6:34 That's when she's your wife 😳
I am a registered Takodachi… but Fauna’s existence and moments like this always challenge that. She’s always on the good stuff
They have zero conflict, as Fauna is nature and takodachis are made of void essence, a purely unnatural material.
I enjoy Fauna telling us about watching the wahvs🌊