Hacking [No longer maintained] RajNX - starter pack for Nintendo Switch

  • Thread starter Thread starter rajkosto
  • Start date Start date
  • Views Views 332,864
  • Replies Replies 1,046
  • Likes Likes 111
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 :P ).
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 :)
 
  • Like
Reactions: adrenochrome
Omg 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 :)

I mean you could say the same about reinx minus the getting their own small changes into mainline part which makes it worse, not better.
 
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 flair
i'm pretty sure it's a thinly-veiled stab at me, but i never call my stashes "meteosnx" and say that i'm making something
 
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 :)

I do plan on creating my own bootloader, because doing things on the BPMP is so suffocating. Until that is finished, why not use the best one currently out there, one that I have already contributed to ? I see no reason why a custom bootloader is required to make something a CFW.
 
I mean you could say the same about reinx minus the getting their own small changes into mainline part which makes it worse, not better.
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

-snip-
 
Last edited by Quantumcat, , Reason: removed deleted post quote
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
Adding an empty file to disable nogc is not in any way better than a proper config-file...
Es patching is rajnx afaik.
 
I 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.
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).

I mean you could say the same about reinx minus the getting their own small changes into mainline part which makes it worse, not better.
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 :)
 
Adding 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.

-snort- our es patching is smaller and faster and only uses one patch file but yeah, it is present
 
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 :)
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.

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).
 
  • Like
Reactions: Deleted User
Do your thing Raj
its always good to have options, lets see what your fork will bring to the cfw game

we all know you know your stuff already
 
  • Like
Reactions: mezz0
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.

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).
You are not wrong, until yesterday I had not had time to work on it :)
Sadly, I have a full time job, and a house to take care of, real world adult responsibilities. I started helping with ReiNX very recently, Rei and calypso were busy working on other parts of the system, and didn't have time to look into patching NSOs in the loader yet, so I asked if I could help when I had a bit of free time. That free time finally came over the last couple days, a couple hours at a time.

Raj, I wish you the best. You are a very smart person, but I think you need to take some time to learn when to pick fights. Nothing good will come out of bickering like this, we should all be trying to work together to improve the scene, not fighting between eachother and making it worse. I think we've all had our fun in the EoF copy of this thread, so I'll leave it at that.
 
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.
As I said, learn to pick your fights. Have a great night.
 
  • Like
Reactions: Quantumcat

Site & Scene News

Popular threads in this forum