Why going ReactOS and WINE so different directions?

[theuserbl]

Why going ReactOS and WINE so different directions?

It isn't only that lowlever parts are different. The programs using different sourcecode, too.
For example the taskmanager
https://github.com/reactos/reactos/tree ... ns/taskmgr
https://github.com/wine-mirror/wine/tre ... ms/taskmgr

It was written until 2001 by the ReactOS-developer Brian Palmer. And it was taken over by WINE.

And then both taskmanager going different ways. Here as an example the file endproc.c of it
https://github.com/reactos/reactos/tree ... ns/taskmgr
https://github.com/wine-mirror/wine/blo ... /endproc.c

It begins in the introdution text of the file, where you can read the different evolution.
In ReactOS

* Copyright (C) 1999 - 2001 Brian Palmer <brianp@reactos.org>
* 2005 Klemens Friedl <frik85@reactos.at>
* 2014 Ismael Ferreras Morezuelas <swyterzone+ros@gmail.com>

and in WINE

* Copyright (C) 1999 - 2001 Brian Palmer <brianp@reactos.org>
* Copyright (C) 2008 Vladimir Pankratov

And then the code.
In the WINE one it includes a lot of more system-headers.

And for example the funtion "void ProcessPage_OnEndProcess(void)". For me they look very different. The WINE-implementation includes an for-loop over all items. ReactOS haven't it there. Which implemetation is better? Or are some parts better solved in ReactOS and other parts better solved in WINE?
Why can't you merge your programs with the WINE ones?
Why was it possible, that in 2001 WINE takes ReactOS code, but later there finds no ReactOS code the way to WINE?

Greatings
theuserbl

Btw: Question also posted on the WINE-Forum at
https://forum.winehq.org/viewtopic.php?f=2&t=28940