If any of this is true they are hurting people who bought or have SX OS "hacked" by a 3rd party and don't come here o know the scene. It's childish, they needed to crack SX OS and release it or copy all it's features, that's cool, not fucking other people's switches, again, if it's real that the 2.0 release it's bugged because of spiked code
It works both ways - if TX stops "borrowing" code and either credits the original authors, or makes it themselves then this wouldn't be an issue. If TX continue - well, you know who to blame and it won't be the original authors; they're protecting their own hard work after all. I'd also go as far to say by spiking their code, they're not "fucking other people's switches" over. They're breaking a feature, yes, but we're still a long way away from bricking the Switch on purpose (ala R4 clone cards and Gateway before). What I mentioned is purely a broken feature TX stole the code to, which is fixable and doesn't actually prevent you using your device at all (and in most features like LFS - will probably affect ~10% of total users max).
Personally, I understand why devs spike their code and I'd personally do the same if I knew someone was making bank off my time and work, without even doing the grateful thing and crediting me (it's free for god's sake!). I wouldn't go as far as to damage devices, but I would make my displeasure at getting my work shamelessly taken without any word by just breaking said feature and stopping at that (as other Switch devs have done). It would be that or take everything private so no one can use it (if you can't be courteous, you can't have in other words).
Should also mention - if they're lazy enough not to test the code they've pasted in, then they don't deserve your money. From what i've read of the commits, we're talking 1 - 2
bytes off an offset. That's incredibly easy to spot if they put the time into testing to see if said code actually ran, but from what I've read - they seem to just have copy, pasted and pressed "compile" and that's it. Out the door! If anything, you should be questioning their programming ability if they were lazy enough not to spot that as it may spread to bigger, and worse things (i.e pasting in code which has a high chance of banning the system etc).
--------------------- MERGED ---------------------------
I wouldn't be surprised either... judging from the maturity level displayed by some of the "free" developers on this forum I am not surprised at all if they are doing something so lame. Instead of everyone sharing knowledge to screw Nin they are playing little teen drama games with each other and purposely sabotaging the scene because some people happen to make money from putting out a popular WORKING real product. The same ones sabotaging are the same ones who haven't put out an official release since Feb.
I can understand where they're coming from (I've had personal projects ripped apart and rebranded by some twat before who soaks up all credit so I know first hand how it feels) and I actually agree with what they're doing. If you're not capable enough to fix said broken code, maybe programming isn't something you should be doing (we're talking simple things here. Offsets which need updating etc).
Also remember - SX OS is closed source, while the other projects who are protecting their work are open. If anything,
TX are keeping the knowledge to screw Ninty to themselves (i.e XCI loader) while other projects TX are shamelessly taking code from are the ones doing the
real innovation (like Tinfoil or ReiNX). Can't innovate if you don't share the knowledge.
Also the one's doing the sabotage is Rei at the moment. He's put out a lot of working releases since Feb (including 1.7 earlier this week). Other devs may follow however.