This has been one of my favorite software projects to watch, because it's such an insanely monumental undertaking and moves so damn slowly. There were people working on this two decades ago, putting in tiny fixes and little bits of code and whatnot, and they did it even knowing that basically nobody would see their work for decades.
Hell, I have never seen a ReactOS installation in the wild, and I'm the kind of person whose friends install Haiku, Nix and NetBSD as their daily drivers. And the second-hand stories I've heard about people who did install React was basically "I was bored, I put it on a drive, played around for 5 minutes, and wiped it."
But that doesn't discourage them. Meanwhile, work keeps going on in the background. So many untold man-hours of thankless work going into the project, and the vast majority of that "hard" work with no payoff for years.
And now it's finally getting close to actual Windows, after decades of work, and soon (well, years, but still) people will be using it everywhere as a replacement for Windows.
This is one of the most important software projects in history. My hat is off to the ReactOS developers, and congratulations on the latest release.
 Here are the names of the 75 programmers that have worked on ReactOS: https://github.com/reactos/reactos/blob/master/CREDITS
What I like about this project, besides the dedication and professionalism of the team behind it, is that it offers PC gamers a possible way to play Windows-era games moving forward. In a decade or two, we likely won't be able to activate a Windows XP machine (and wouldn't want to with all of the security hazards either) so it's great to have a free and open source project to run our Windows stuff.
I feel like ReactOS has gained more attention lately and hope some of it will spill over to support of this project. It’s a bit like you need to reach a critical mass in features and usability, and until then it’s an uphill battle to maintain enough traction. Haiku is another cool project, especially as someone who will always have a warm spot left for the Amiga. But until the long waited for beta is out, I think they have an ever more dangerously steep uphill path to climb.
One day when Windows drifts too far away from its golden age functionality, it will be great if ReactOS can fill the gap. However, I feel like MS could one-up them overnight by providing a sandboxed 32-bit XP VM as part of current windows. We’d get back DOS support and compatibility with old programs would be better. Call it Windows Subsystem for Windows or whatever. That would also pave the way to removing a lot of Win32 cruft from the main codebase, which MS seems very itchy to do.
> Several bugs have been squashed in the ReactOS CC and Freeloader, allowing it to boot in 96MB hardware (smaller RAM need than our 0.4.7 release).
This is an impressive update when most projects, and not necessarily wrongly, always move in the opposite direction. Good to see.
As a free Unix user I'm primarily interested in ReactOS in order to test certain Windows things such as cwrsync over ssh. I tried installing ReactOS about a month ago but didn't have the right hardware to make it through the installer. I will definitely try again.
Windows 10 is still not a good option for embedded x86 systems even in its proper supported embedded mode. Once I've replaced the shell, turned off all the services and junk programs and opened the one port on the firewall my industrial touchscreen application requires I would really rather windows take the hint not to change anything and leave things be.
I have been keeping an eye on Reactos for over 10 years, it is still a promising candidate for my legacy systems, USB Install would still be good to have as it is painfully hard to get it on to newer systems which don't have Optical drives.
It took me a while but I can now compile my gui applications for Linux, so going forward that is my strategy, but lots of factories out there still scared to move off windows XP and Reactos would be ideal.
With the US Court of Appeals for the Federal Circuit ruling that API's are copyrightable I wonder what type of impact it could have on open source projects, such as ReactOS, if the copyright holder ever decided to take action.
One of the most interesting changelog that I have read in a While. Well written, thoughtful and gave me good insight into the project.
I've submitted non-clean-room reverse engineered code to ReactOS years ago when I was younger and it was accepted with no questions asked. But since that day, I can't bring myself to believe all of this is clean-room reverse engineered.
I hope it was an outlier event and that external contributions are better audited today.
Genuine question: What advantage does ReactOS provide over Wine?
https://www.reactos.org/wiki/WINE explains a bit but still doesn't answer the question.
P.S. oh by the way, the developers of both projects are apparently collaborating and ReactOS uses Wine's DLLs for their userspace, so my question is not meant to criticise the "double-effort" or anything like that.
The USB support isn't quite there yet (major rework didn't make it this release) but otherwise this is a pretty good release with massive progress in actual usefulness.
Tried the livecd in a VM and a couple of niggles sprang up.
First of all, no driver for the network card in Virtualbox, though Vmware worked fine.
Second, no web browser...
Third, the mouse sometimes freaked out and got stuck in a corner.
I’m curious - so now that the ReactOS guys are picking up bugs in Windows, does this mean they have a comprehensive test suite of Microsoft Windows proper?
I'm willing to bet, this will be very useful in a few years time, and the primary use will be 'fixed function' devices (in industries that are very slow to change) that currently require Windows. (ATMs, POS, Announcement Screens, Equipment controllers, SCADA systems, etc, etc)
I think their site is getting the HN hug of death, loads extremely slow/doesn't load at all...
I think Windows will just keep breaking compatibility faster then they themselves and others are able to keep up. Forcing users to keep upgrading and buying the same software over and over again.
I wonder if the planned Vista/7/10 support will extend to kernel mode drivers, especially for WDDM2 and up graphics drivers.
Currently, the supported graphics drivers is pretty sad for modern-ish hardware on ReactOS, because they are limited to drivers for Windows Server 2003 / Windows XP, which aren't available for a lot of modern cards (or integrated chips, for that matter). Additionally, a lot of the older XP drivers don't work well on ReactOS today.
I love ReactOS, especially in VM. Windows requires separate license for each VM. If I maintains 10 VM for testing, it's a problem.
In case you are dismissing this as a fringe project, remember, what is ridiculous today is commonplace tomorrow.
I'd be curious if ReactOS runs the Oculus Rift drivers, runs docker and is more performant then Windows 10.
Can anyone comment if I can install old Windows 2000 games on this, like C&C Red Alert? Would it work?
What Kernel does this OS use? What's its history? Is it a unix fork such as Linux?
appears to work well, including old photoshop 5.5 from a windows cd https://youtu.be/Ne88Is2cymQ
Does Starcraft run?
So I'm a ReactOS fanboi, but... but...
- You need to fix your flaccid dev community. Your forums have a terrible S/N ratio. IRC may be great and all, but I don't see any hard documentation behind any design discussions or development. I do see crazy shite like "can I run ReactOS on Playstation 2". The forums make your project seem dead, which it clearly isn't.
- You need to fix your flaccid dev community. It needs a larger presence. It needs to be tangible (who is doing what? who are the people? do you have conferences?)
- You need to fix your flaccid dev community. There is a bunch of really useless, out-of-date, confusing and out-right self-inconsistent information on building ROS, and the Git move didn't help (but kudos on the move, it is long overdue). I've tried 4-5 times to do something, but the directions I followed on Win, Ros or Linux all ended up breaking somewhere.
- You need to fix your attitude problems (or your forums). There are people asking reasonable questions, who get actively or passively aggressive answers. Not good.
- You need to fix your toolchain problems. This whole SEH thing is getting out of hand. Does Clang support SEH yet? It might - https://clang.llvm.org/docs/MSVCCompatibility.html. So maybe you need to bail on GCC, or maintain your own fork of it (yes, it's ridiculous that GCC still doesn't have SEH support, and the patents have long expired).
- You need to get a grip on x64 support. Your toolchain problems cannot be a gate (and you can clearly use MSVC for building... so...). IA32 support is great and all, but needs a back seat to x64.
- You need to get a grip on UEFI booting (note UEFI booting does not /necessarily/ mean you need improved ACPI support, in practice)
- Forget Xbox, NewWorld PowerMacs (those were BE anyway) and 32-bit Arm chips (which outside of the Pi are too varied and too few). Targeting 64-bit Arm chips does make sense, though, now that Microsoft has released a client build of Win 10 on laptops and an Arm server vendor demoed Windows Server at OCP'18 (http://www.opencompute.org/assets/Uploads/18150J-Ampere-PPT-...). You will need UEFI and reasonable ACPI support to support ARM64. You can target SBSA and SBBR compliant systems and this will give support for the entire server ecosystem (and qemu VMs, har har).
- You might wish to minkernel-ize ROS as well, so you can boot without a GUI.
- You might wish to update Wiki (and build a list of links to relevant pages) for active subprojects.
For those of you who would like to run pen tests on safe ip addresses here is a list: http://bit.do/rhemgla
Every time I see this I briefly think it's a Linux distro with a React-based window manager