Linked by Thom Holwerda on Wed 15th Nov 2006 20:04 UTC, submitted by fireball
ReactOS ReactOS, the open source implementation of a Windows XP/2003 compatible operating system, is announcing a start of a series of interviews with ReactOS developers. The first published interview features the project coordinator Aleksey Bragin. The ReactOS team plans to publish interviews on a weekly basis.
Thread beginning with comment 182697
To view parent comment, click here.
To read all comments associated with this story, please click here.
umccullough
Member since:
2006-01-26

Wine practical runs no Windows software at all.

Well, it's a good thing ReactOS doesn't use Wine in any way, shape or form then... because that would make ReactOS just as incompatible

</sarcasm>

Fact is, ReactOS and Wine are attached at the hip.

Reply Parent Score: 4

Alleister Member since:
2006-05-29

Wine does have to do much more abstraction work then Reactos, because they actually try to map windows functionality to existing Linux functionality while Reactos simply tryes to offer an completly compatible environment.

So Reactos has a chance to be compatible some day, while the same is rather unlikely for Wine.

And Reactos *does not* use Wine, they just cooperating at librarys.

Reply Parent Score: 1

umccullough Member since:
2006-01-26

And Reactos *does not* use Wine, they just cooperating at librarys.

ReactOS very much uses Wine - they sync with Wine code all the time (just look through their changelogs).. Maybe your definition of "use" is different than mine - but if you use code from a project, you're using that project I think.

So basically what you meant to say was "Wine by itself doesn't run much windows software" - which would be a more correct statement... and it really wasn't meant to - thus all the confusion here. Wine is mostly an open-source reimplementation of Windows APIs and libraries. It is not an OS.

Edit: typo

Edited 2006-11-16 20:45

Reply Parent Score: 1

Alleister Member since:
2006-05-29

"ReactOS very much uses Wine - they sync with Wine code all the time (just look through their changelogs).. Maybe your definition of "use" is different than mine - but if you use code from a project, you're using that project I think."

Which doesn't mean that they inherit their compatibility problems, if those problems don't arise from those parts that they are using. That is rather obvious, isn't it?

What i mean by not using wine is, they don't just run an arbitrary OS and Wine on top of that. They using parts of the wine Librarys but they don't use their Linux abstraction layer which is likely the source of most compatibiltiy issues.

"So basically what you meant to say was "Wine by itself doesn't run much windows software" - which would be a more correct statement... and it really wasn't meant to - thus all the confusion here. Wine is mostly an open-source reimplementation of Windows APIs and libraries. It is not an OS."

Ahhh ok, now i understand. They don't want to archieve compatibiltiy, they just think that ugly dated WinAPI is sooo beautifull. Now that makes sense.

Reply Parent Score: 1