Editing ReactOS (section)

====Wine cooperation====
[[File:Wine on ReactOS.svg|thumb|300px|A simplified architecture diagram of ReactOS, with Wine dependencies indicated by the Wine logo. White boxes denote third-party binary software. Green boxes are "[[user space|userland]]" components, red are kernel components.]]
The ReactOS and the [[Wine (software)|Wine]] projects share the goal to run binary Windows software natively and can therefore share many dependencies and development.<ref name=collaboration2>{{cite web |url=https://www.winehq.org/interview/14 |title=Interview with Steven Edwards |first=Brian |last=Vincent|date=2004-05-15 |publisher=winehq.com |quote=''BV: Wine and ReactOS have had a mutually beneficial relationship. Is there anything Wine could do different that would help ReactOS development?[...] BV: You guys have certainly contributed a lot of your work back to Wine, including some of the utilities you've written. For instance, the task manager was recently ported from ReactOS. Do you guys have any plans in the works for developing more tools? Steven: I really want to see a solitaire clone make it in to Wine and ReactOS.[...] At some point we are going to have to develop replacement components for everything in Windows so if there is a program that Wine needs and ReactOS implements it then I will try to make sure it's released under a compatible license.'' |access-date=2016-01-06}}</ref><ref name=wineackn /> ReactOS uses portions of the [[Wine (software)|Wine]] project so that it can benefit from Wine's progress in implementing the [[Windows API#Versions|Win32]] [[Application programming interface|API]].<ref name="wineackn">{{cite web |title=Acknowledgements |url=https://wiki.winehq.org/Acknowledgements |access-date=2009-11-15 |publisher=Wine}}</ref> While Wine's [[Native API|NTDLL]], [[Windows USER|USER32]], [[Microsoft Windows library files#KERNEL32.DLL|KERNEL32]], [[Microsoft Windows library files#GDI32.DLL|GDI32]], and [[Microsoft Windows library files#ADVAPI32.DLL|ADVAPI32]] components cannot be used directly by ReactOS due to architectural differences, [[Snippet (programming)|code snippets]] of them and other parts can be shared between both projects. The kernel is developed by ReactOS separately as Wine relies here on existing [[Unix-like]] kernels.<ref name="waterloo">{{cite speech |url=https://csclub.uwaterloo.ca/resources/tech-talks/reactos-an-open-source-os-platform-for-learning/ |author=Ionescu, Alex |title=The ReactOS Project – An Open Source OS Platform for Learning |location=University of Waterloo, Canada |date=2006-02-26 |access-date=2009-12-10}}</ref><ref name="notwindows">{{cite conference |last=C. |first=Michele |date=2009-06-19 |title=ReactOS is (not) Windows |url=https://www.hackmeeting.org/hackit09/presentazioni/ReactOS_is_(not)_Windows.pdf |conference=Hackmeeting 2009 |location=Milan |access-date=2020-10-20 |conference-url=https://hackmeeting.org/hackit09/}}</ref>

Separately, the experimental ''Arwinss'' branch was created as an alternative means to improve USER32 and GDI32 support through an alternative implementation of the Win32 API. Whereas ReactOS's original Win32 subsystem was closely modeled after its equivalent in Windows, Arwinss combines the architecture of that subsystem with the corresponding implementation in Wine. To this end, Arwinss uses Wine's GDI32 and USER32 libraries with few changes to take fuller advantage of Wine's existing software compatibility. Arwinss also allows the user to optionally use a remote [[X Window System|X server]] instead of a local display.<ref>{{cite web |last=Holwerda |first=Thom |date=2010-01-18 |title=ReactOS Proposes Radical New Win32 Subsystem |url=https://www.osnews.com/story/22750/ReactOS_Proposes_Radical_New_Win32_Subsystem |access-date=2010-01-18 |publisher=[[OSNews]]}}</ref>