![]() This is especially important when using emunand. You gain literally nothing except a slightly higher chance of your fuckups actually having more sever consequences. Tl dr: There's no reason to use a "more" error prone technology "just because it's newer". It's like saying "Don't use seatbelts, I am driving since 20 years and nothing ever happened to me! It's just additional work which isn't worth it." But even then, isn't almost everyone using tinfoil nowadays anyways?Īlso the general argument "I am using it and nothing bad happened to me" is absolutely backwards and the worst sentiment you can have. Like most people pointed out, there's literally no reason to use exfat unless you are using big XCI's which would only apply to SX users. It's a general sentiment that newer = always better while ignoring all the drawbacks. If the chances for the file system to corrupt is even 1% higher than FAT32 it's not worth to upgrade "just because it's new". Same goes for "Using new technology 'just because'" is not the way to do it either, especially if said technology is more prone (even if it's unlikely) to error. > Using an old technology "just because", is not the way to do things. The answer is I've never corrupt it, or had to reformat or recover from any error. Should be noted that I use the card and system much more than normal end-users, so any argument of "you just don't use it as much or you don't do X or Y as much as I do", is out the window. Ask me how many times my 400gb exfat, with emunand, homebrew, emulation, xci mounting, and installed nsps has corrupt since the beginning. I am telling you this as a technician, and as a user. Unless you do something stupid while writing into the card, you won't corrupt. Exfat is better than Fat32, in every way. It is literally just a way of keeping the plebs at-bay (no disrespect).įrom here, everyone decided to take it into their own understanding, and just started saying that "exfat is broken, don't use it, fralala". So, to avoid any further issues, developers started requiring fat32 cards. So, if the homebrew crashed, or you did some stupid shit (majority of the cases were user error), your partition table could corrupt. So, back in the day, homebrew like retropie would constantly be writing to the sd card, even if nothing was processing. ![]() I won't get into it, but basically cached writing vs direct writing over 2 phases. Now, the way exfat works, is slightly different than fat, in the way it writes, and verifies the data. They would force close apps, shut off the switch while running something, or in the earlier days, their switch software would crash with homebrew running. The problem is, that many people were using theirs switch and/or sd card incorrectly. So there is nothing wrong with exfat, or the exfat driver. Coming from a developer's standpoint.Īs you already know, the file limitations, blah blah blah, not going over that again.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |