It does indeed come with additional files, I won't argue with that. That is what starter packs do, they bundle up other peoples unmodified files, sometimes with their own small files added here and there, to get people started.It has additional patches and Raj integrated a bunch of his work into the unterlying projects.
It has about as much of a right to call itself cfw as a certain other cfw which is basically just a bootloader + atmosphere sysmodules (and more features ).
It does indeed come with additional files, I won't argue with that. That is what starter packs do, they bundle up other peoples unmodified files, sometimes with their own small files added here and there, to get people started.
However, getting code into mainline Hekate/Atmos doesn't make this his own CFW, it means he is helping contribute to those projects, both of which already have their own topics
additionally, how does a package consist of a release under the definition of the flairIt does indeed come with additional files, I won't argue with that. That is what starter packs do, they bundle up other peoples unmodified files, sometimes with their own small files added here and there, to get people started.
However, getting code into mainline Hekate/Atmos doesn't make this his own CFW, it means he is helping contribute to those projects, both of which already have their own topics
listed it in the featuresOmg rajkosto CFW! I love your work dude! This is a good news.
What does this CFW have against ReiNX 1.0 or Hekate + sig patch?
It does indeed come with additional files, I won't argue with that. That is what starter packs do, they bundle up other peoples unmodified files, sometimes with their own small files added here and there, to get people started.
However, getting code into mainline Hekate/Atmos doesn't make this his own CFW, it means he is helping contribute to those projects, both of which already have their own topics
you should check again, my bruI mean you could say the same about reinx minus the getting their own small changes into mainline part which makes it worse, not better.
Adding an empty file to disable nogc is not in any way better than a proper config-file...you should check again, my bru
reinx is now much, much better, we have layeredfs, es and fs patching, as well as a toggle for nogc, and all without shitty config files
You are a better programmer than to think the only things changed in other CFW is folder namesI kept the folder name atmosphere so that it remains compatible with the currently-existing community work (where you add more exefs overrides to).
Apparently changing this folder name is something i must do to abide by your definition of CFW.
Hm, or, now hear me out, ReiNX has a different idea in mind, and is just getting started. So we have forked off of existing code (Why reinvent the GPL'd wheel?), and are slowly working towards our vision, because it doesn't align with the vision of the other CFW developers. Not being able to get code into mainline isn't a bad thing, and is often what leads to forks. I will just assume you are new to the open source worldI mean you could say the same about reinx minus the getting their own small changes into mainline part which makes it worse, not better.
i installed devmenu nsp just finegood old nsps worked?
reinx added the es patching early this morning as well as testing it over the last few daysAdding an empty file to disable nogc is not in any way better than a proper config-file...
Es patching is rajnx afaik.
Sure it is. A config file is scary to an end-user, having a blank file is as easy as pressing delete. No room for error.Adding an empty file to disable nogc is not in any way better than a proper config-file...
Es patching is rajnx afaik.
I am not new to the open source world, I'm just saying that getting stuff mainlined is not an indicator of how 'CFWy' something it.You are a better programmer than to think the only things changed in other CFW is folder names
I've asked multiple times if you have plans in the future to actually fork/develop this away from Atmos/Hekate, because if not, then this is just a pack. If you do, then it's a WIP CFW (At best, depending on timeframe). But what it is not, is a CFW Release (Which is what you have it tagged as).
Hm, or, now hear me out, ReiNX has a different idea in mind, and is just getting started. So we have forked off of existing code (Why reinvent the GPL'd wheel?), and are slowly working towards our vision, because it doesn't align with the vision of the other CFW developers. Not being able to get code into mainline isn't a bad thing, and is often what leads to forks. I will just assume you are new to the open source world
You are not wrong, until yesterday I had not had time to work on itI am not new to the open source world, I'm just saying that getting stuff mainlined is not an indicator of how 'CFWy' something it.
https://github.com/Reisyukaku/NX_Sysmodules/commits/master < until yesterday all the changes to the sysmodules literally were the names (and the normal no-exosphere-patches).
As I said, learn to pick your fights. Have a great night.While I do not see how rewriting other people's work just to call it your own is "improving the scene", you all have your reasons.
As it stands, this RELEASE has as much right to be called as CFW as any other posted on this forum.