2

I have heard expressions such as ".NET FAT32 client" or ".NET FAT32 application". When i asked what was meant by that, the answer was "a desktop application". This however makes little sense to me. FAT32 is a file system such as NTFS. Wouldn't it make more sense to say "NTFS application" due to the popularity of NTFS compared to the old and deprecated FAT32 ?

Dante
  • 10,722
  • 16
  • 51
  • 63
  • 1
    This isn't referring to the `FAT` as in `File Allocation Table`. It's referring to the client containing all the code and logic (and therefore being `fat` as in overweight), instead of being a `thin` client that passes off most of the work to the middle tier or a server app. The `32` means it's a 32-bit FAT client. See [here](http://en.wikipedia.org/wiki/Thin_client) for a description of `thin client`. – Ken White Feb 07 '12 at 18:15
  • You sure it wasn't WIN32 instead of FAT32? Win32 makes sense, Fat32 makes none. Or maybe you heard from someone who didn't quite know what he was talking about. – Joel Coehoorn Feb 07 '12 at 18:15
  • 1
    @KenWhite: Can you point to any resource that combines "Fat" and "32" into "FAT32" in order to refer to a 32-bit desktop application? – Adam Robinson Feb 07 '12 at 18:17
  • @Adam, no. :) I'm thinking the questioner accidentally combined two different things because of his not understanding the original conversation he heard. :) That's why I posted a comment instead of an answer, BTW. – Ken White Feb 07 '12 at 18:19

3 Answers3

4

The term Fat client refers to a desktop application usually written as a native application for the user's platform.

"FAT32 application" doesn't make sense. As you say, FAT32 is a filesystem. However, "Win32" refers to a 32-bit Windows application (which is a common implementation choice for a fat client on Windows). I suspect the speaker might have conflated "Fat client" and "Win32 application" into "FAT32 application", which doesn't make sense. Either that, or the speaker actually said "Fat Win32 application".

Greg Hewgill
  • 951,095
  • 183
  • 1,149
  • 1,285
2

".NET FAT32 client" is gibberish. As you say, FAT32 is a file system and has nothing to do with .NET or the nature of the application. Applications are not distinguished by the file systems on which they operate, so "NTFS application" is as nonsensical as the other term.

Adam Robinson
  • 182,639
  • 35
  • 285
  • 343
2

Whoever was talking to you was misinformed, most likely they where referring to Win32 which is the Windows 32 bit API. However when working with .NET you normally do not work with the windows API directly unless you are doing P/invokes. This would apply to C++ applications mainly.

Scott Chamberlain
  • 124,994
  • 33
  • 282
  • 431