I doubt it would affect us, but it is too early to tell. We don't know what their kernel is really like inside and thus we might avoid all this in the first place. Or, due to independent invention, we might stumble into it by mistake.

Maybe, but their first 2 posts had nothing to do with ROS.

I propose that the category heading be changed to something like, "Other ReactOS Discussion". We get so many folks off the streets who see "Off-Topic" and think it's a place for general chit-chat.

Well, we are a 32-bit OS, and thus should be able to run 16-bit apps. Plus, we have the x86 emulator in the NTVDM and should be able to run 16-bit apps in there already, even if we were to build as 64-bit.

I doubt we can do all that once we reach an NT 6 target with the audio drivers.

Okay, maybe not the best comparison on my part, but maybe you get my point. GNU used Linus Torvald's kernel originally because it was ready at that point, like some Microsoft code is freely available. However, GNU was going to write their own kernel. So if those who don't like us using Microsoft ope...

As for using open sourced Windows code, I think we should use it now. If some take issue or there are purists, then they can code their own replacements. That's much like GNU+Linux vs. GNU Hurd.

Well, not sure if nlite will work with ROS yet.

But you know, if someone wanted to volunteer such, it might open ROS to more testers, since it could mean more hardware. And without the knowledge to fully implement replacement microcodes, that could be used for CPUs with fatal SSE2 bugs, for instance, if they exist. Or maybe certain newer CPUs if ...

I don't remember. I thought they had removed any such instruction. Plus you can compile it yourself. Oh, you mean if an app requests it. Shouldn't that depend on the CPU you have? If your CPU doesn't have such instructions, I don't think ROS will emulate them. I remember the x86 machines that lacked...

Or clear your cookies.

As mentioned by elhoir - JIRA is not the place for such discussions. If you'd like to propose it in one go, I suggest going the mailing list way or keep discussing this topic until a developer either takes interest in it or gives a final word on it. I don't understand why the feature request was cl...

I am not trying to hijack in saying this reminds me of the situation with Doom 3. They accidentally, by independent invention, copied some of Creative Lab's patented rendering code. So ID software paid them a license fee or whatever, as that was cheaper than going to court. But then they finally dec...

I think post to the forum can get a wider reading and reply than JIRA. No, that is not the point. Jira is for reporting bugs or desired features, and the developers rarely look in here. So you want to get it before the eyes of those going to code it. It doesn't need an audience any wider than the d...

However, FreeWin95 never had any lines of code committed. As for this end, yes, they came up with better tools and methods. From what I read, they've come up with all sorts of new tests, started using precompiled headers to speed up the builds and thus let devs test it sooner to make sure they didn'...

Yes, LAV tends to offer better performance and stability unless you have a specific reason to use the others. There are times when you are better off with the Microsoft and Intel codecs, but that's mainly in more exotic situations or media using more arcane features. As for PhysX, I am not sure how ...