We're among a9lh users here, go tell that to menuhax usersPeople need to learn not being so scared, lol. Touching your sysNAND's not gonna kill it.
JK
Of course you shouldn't apply this to everything in life. But here, it's more "it ain't late in terms of functionalities so don't change it".That's a terrible way to think about things lol.
Our planet would be in a terrible condition if more people thought like that.
Yes and no. Because the NAND restoration as a very low percentage of failing, but if it does fail while you're (the "you" isn't you but the user, I just say "you" because it's easier to write than "the user" everytime) restoring sysNAND and a9lh (or if you flash weird stuff because you're not the smartest person on Earth), you're done. While if you never touch your sysNAND once a9lh works, even without being scared of Nintendo and stuff, you avoid every problem. Even in the case all your backups are corrupted and your emuNAND is corrupted (because you made a lot of dumb choices in life ), you can create a new one. But you can't create a new sysNAND.People telling you about Nintendo ever breaking your 3DS, not possible. Certain CFWs block FIRM1/FIRM0, so an update will never be able to touch it.
"But what about when NATIVE_FIRM gets updated?" You'll get the same result as if you were running emuNAND. Your NAND will not boot until CFW devs update it to work with the latest FIRM. If you're feeling impatient, flash an older NAND backup, almost the same way you'd do on emuNAND.
So yeah, even in the case of shit happening due to the user's fault (not Nintendo's, not CFW authors, but the user), nothing bad can happen as long as it is in emuNAND. So of course, "don't be dumb" is a valid argument, but "no need to avoid being dumb when I can just be safe" is a better one to me