Look at the commits. The only changes are the readme, two file paths, and a bunch of removals..
Look at the readme of the first AuReiNAND. There wasn't much to that as well.Look at the commits. The only changes are the readme, two file paths, and a bunch of removals..
It's not the amount of code you wrote/deleted, it's the outcome. I've given proper credits. Pointing out the bad stuff is fine, but all you have is not even constructive criticism, please leave the thread. If think you can do better, please do, so we all benefit from it.Look at the commits. The only changes are the readme, two file paths, and a bunch of removals..
Umm, look at his "first release" commit. He didn't even fully strip it right. There's still emuNAND references.Look at the readme of the first AuReiNAND. There wasn't much to that as well.
People want options, if you don't like that, then you can go somewhere else. If you don't like that there's another CFW, then that's tough shit for you because it's already been made and a thread has already been posted. No amount of pissing and moaning is going to change that.
It's still a first release, give the guy a break. Like I just said before, it's too late now for your pissing and moaning, it's already been made and released. If you don't like that fact, then sucks to suck.Umm, look at his "first release" commit. He didn't even fully strip it right. There's still emuNAND references.
Porting it to O3DS wasn't easy though (for a programming newbie). Especially since I also had to port the reboot patch and make it configurableAuReiNAND started out a nothing special CFW that only ported ReiNAND to the old3DS.
People want options, don't damper them because you don't want options.
Release. As in it should at least do what it says right. Now bugs are a different story, but at least do it right.It's still a first release, give the guy a break. Like I just said before, it's too late now for your pissing and moaning, it's already been made and released. If you don't like that fact, then sucks to suck.
So now it's a semantics argument? You're complaining about nothing now.Release. As in it should at least do what it says right. Now bugs are a different story, but at least do it right.
I'd like to thank you publicly for your great work on ARN.Porting it to O3DS wasn't easy though (for a programming newbie). Especially since I also had to port the reboot patch and make it configurable
If you have updated sysnand, yes, this has reboot patches. It will work out of the box if you install it the way I explained in the readme (on github)I have a 9.2 sysNAND but would love to use this for GBA (it is AuReiNand without the built in loader), but launching any GBA results in an error has occurred screen. Can you only use this with updated sysNAND?
What's one thing that ShadowFW doesn't do?Release. As in it should at least do what it says right. Now bugs are a different story, but at least do it right.
That "nothing" is redundant code in a "minimalist" CFW because someone didn't bother removing the code before making a "release" to stroke their ego.So now it's a semantics argument? You're complaining about nothing now.
Porting it to O3DS wasn't easy though (for a programming newbie). Especially since I also had to port the reboot patch and make it configurable
What does it not do? The one thing thing that makes it special. It's minimalism. You have redundant code all because you didn't restructure it.I'd like to thank you publicly for your great work on ARN.
--------------------- MERGED ---------------------------
If you have updated sysnand, yes, this has reboot patches. It will work out of the box if you install it the way I explained in the readme (on github)
--------------------- MERGED ---------------------------
What's one thing that ShadowFW doesn't do?
I wasn't undermining your work, just simply pointing out that just because a project starts out as something "small," doesn't mean it can't grow a life of it's own. Your project started out as simply porting ReiNAND and now it's become the go-to amazing CFW on it's own and stands out from it's parent project.Porting it to O3DS wasn't easy though (for a programming newbie). Especially since I also had to port the reboot patch and make it configurable
Simply dumping on a project because it doesn't appear like much isn't the right approach. You are taking this project apart because you don't think it's needed. There is a drive for more choices when it comes to CFW's and people are filing that need.Release. As in it should at least do what it says right. Now bugs are a different story, but at least do it right.
Oh wow. It's failing because I didn't go and remove that "u32 emunand" thing in one file (among many). I can't believe. /sWhat does it not do? The one thing thing that makes it special. It's minimalism. You have redundant code all because you didn't restructure it.
Not only that but he's made what is pretty much the best CFW out there.You're coding in ARM ASM and call yourself a newbie? You're being way to modest for your awesome work here...
Your argument is weak, so you decided to fall back to ad hominem. Good work.That "nothing" is redundant code in a "minimalist" CFW because someone didn't bother removing the code before making a "release" to stroke their ego.
There's never enough CFW's! The community always needs choices.I think we have enough CFW...
She's*Not only that but he's made what is pretty much the best CFW out there.
Technically the only ASM I've done is changing the reboot patch to boot a payload instead of a patched FIRM (and thus removing all the FIRM copying stuff and adding a jump), and then adding a fallback to the .dat. I know very little ASMYou're coding in ARM ASM and call yourself a newbie? You're being way to modest for your awesome work here...