Ged wrote:
Zachary Gorden wrote:
Just because Windows was tolerant of this
specific sloppiness doesn't mean
we should be.
I completely disagree.
We need to replicate the Windows API as closely as possible, warts and all.
This is what compatibility is all about
Ged.
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev
My view is that we should implement ReactOS as 'the way Windows should
have been' this could lead to faster or more stable environment. I also
realize that Windows has a need for the warts in terms of compatibility.
so What I think would make both camps happy (plus help troubleshooting
issues in the future) is either make ReactOS correct, and release a
'warts compatibility patch' that tries to implement the bugs for
compatibility.
the other option would be to put the bugs for compatibility in, but have
a program built into ReactOS that enables/disable the bugs for
compatibility. This will do 1 major thing for the developers, it'll
allow them to fix every bug without wondering if it has to be there for
compatibility.
I intend to switch to ReactOS as soon as it's ready, in a perfect world
ReactOS (atleast as I see it) would retain compatibility without the
problems of Windows. I know this isn't a perfect world, I just hope my
suggestion is of help.