|
I was interested in helping, too, and I set out to fix some obvious UI bugs, which turn out to be bugs in Wine. The Wine devs are not the same people, and they take a long time to review patches, if at all. I thought the kernel aspects would be interesting, but they were really trying for driver-level compatibility with Windows NT, which means that they have to have essentially the same operating principles, etc. For some reason, I didn't want to make a line-for-line clone of Windows itself. After all, OSS people are always talking about how we would do it better. If the goal is to be able to use the proprietary drivers supplied with some kind of hardware on a mostly OSS base, that's a decent goal. But if you want to be able to run it with complicated software that uses a lot of Windows APIs, etc., it's a fools errand. However, I found it interesting how ReactOS could be used to teach Microsoft devs about Windows internals, even if it wasn't exactly the same. That sort of blew my mind. When you have a bunch of trade secrets, you don't really want the whole company to have access to the code, I guess, and so you benefit from having an open source clone to point to when you want to say how something like a Mutex is really implemented. |