My question is, how is this guide any different from the official SDfiles setup guide located >
HERE
Which is their official guide for running their files (which you link in your guide) not to mention their guide is layed out in a easier to read format and takes you through each step
My guide provides (although by proxy, as that is not my guide) better long-term methods of getting into RCM w/ screenshots on how to set up each (the thread sdfiles links mainly offers options that will likely result in damage to the joycon rail over time, such as paperclip and screwdriver solutions). The guide I link for RCM provides links to where it's possible to buy reliable jigs,
In addition, my guide has users set up a "bootkit" folder (basically a folder that has f-g, TegraRCMSmash and a couple of launch scripts) that turns booting CFW into a "put Switch in RCM, connect to computer and run the sh/bat file" process (on Windows, this is just double clicking a file), which is faster/easier than navigating a GUI every time someone has to boot CFW, and since Hekate is pretty much the only f-g payload you'll need (since it lets you chainload other payloads), it's easier/faster to replace Hekate's payload with an update each time (which a user would have to do regardless when updating the payload).
I also fully provide the option for Android/chromeOS users, which sdsetup only refers to in passing.
I fully have a guide for setting up reboot_to_rcm (the 1.0.0 software side solution), which SDSetup at the moment doesn't provide at all (the thread thats linked that mentions reboot_to_rcm just links to reboot_to_rcm's repository), which although not
entirely noob friendly (it's just not possible to fully simplify the concept of terminals, IPs and DNS, although I did try my best), should get users into RCM mode in a reliable way.
My guide also provides instructions for joining together the partial NAND dumps for Hekate.
My guide also doesn't have users set up AutoRCM, as AutoRCM brings it's own caveats, particularly w/ battery drain and what happens when the battery dies fully.
That and my guide leaves users with a single setup, which is easier to troubleshoot than if someone is running all kinds of setups at once.
Basically, in the end, mine is more of a streamlined process that sets users up with a preset CFW, offering the majority of desired features (homebrew, layeredFS, FTP) which can be easily troubleshooted (which was a big factor for me when writing this guide, mangled SD setups are already common on the 3DS, and the Switch is no different), compared to SDSetups more "hands-off, pick your own system completely if you think you know what you're doing, but here are some potential defaults" (which has the disadvantage that a lot of people think they know what they're doing and will make their own setups, which will just result in a very painful troubleshooting process when it becomes apparent that they don't) approach.
