The only reason I'd work on it would be the learning experience. Sometimes to understand why things are done the way they are, you just have to build your own version of it. Windows sure has a bunch of interesting architectural properties.
Last time ReactOS came up here some folks were concerned about legality too, and I think there even was a salty Microsoft employee ranting about stolen code from the source leaks. I don't think ReactOS will ever reach the point of being a viable Windows replacement, so nothing Microsoft needs to be afraid of. I can somewhat see how you're personally offended that someone stole your code and doesn't credit you (but then again that wouldn't be exactly smart in that case). Best case for Microsoft is that ReactOS raises future Microsoft devs for free. Just check the progress every now and then, if someone stands out, hire them.
> Last time ReactOS came up here some folks were concerned about legality too, and I think there even was a salty Microsoft employee ranting about stolen code from the source leaks.
Link to the actual dicussion here with the comments of the MS employee:
I have the same feeling. They say they don't think about taking it to ourt as ReactOS is too small to pose threat yet. But once they do, I bet it will become another SCO story: years of accusations without any substantial proof.
Last time ReactOS came up here some folks were concerned about legality too, and I think there even was a salty Microsoft employee ranting about stolen code from the source leaks. I don't think ReactOS will ever reach the point of being a viable Windows replacement, so nothing Microsoft needs to be afraid of. I can somewhat see how you're personally offended that someone stole your code and doesn't credit you (but then again that wouldn't be exactly smart in that case). Best case for Microsoft is that ReactOS raises future Microsoft devs for free. Just check the progress every now and then, if someone stands out, hire them.