So Hexkyz discovered brick code in SX OS which I believe further lead to the discovery that SX OS creates a random password on the eMMC (correct?).
So what I'm wondering is what issues could this cause for somebody who first used or tried SX OS but then went onto use Atmosphère once it is released?
I was tempted to use SX OS especially if by Late-October nothing matching it (Atmosphère surely will be released by then I hope) with similar capabilities to do what SX OS can do in regards to 'backups'. Now hearing there is brick code and that SX OS creates a random password on the eMMC is it even worth using at all when Atmosphère will one day likely take over when SX OS loses support?
Just to make it clear I'm not 100% sure on what the eMMC is, to begin with, which is why I'm asking this question if anyone even knows the possible implications due to this.
To summarise my question I'm asking if SX OS creating a password on the eMMC could cause issues with Atmosphère in the future if switching over.
So what I'm wondering is what issues could this cause for somebody who first used or tried SX OS but then went onto use Atmosphère once it is released?
I was tempted to use SX OS especially if by Late-October nothing matching it (Atmosphère surely will be released by then I hope) with similar capabilities to do what SX OS can do in regards to 'backups'. Now hearing there is brick code and that SX OS creates a random password on the eMMC is it even worth using at all when Atmosphère will one day likely take over when SX OS loses support?
Just to make it clear I'm not 100% sure on what the eMMC is, to begin with, which is why I'm asking this question if anyone even knows the possible implications due to this.
To summarise my question I'm asking if SX OS creating a password on the eMMC could cause issues with Atmosphère in the future if switching over.