I still don't really understand the advantage of ReactOS in any particular situation, although I suppose if you really liked NT-era Windows (and people do) it's a re-enactment society for that.
In addition to the compatibility point that someone explained, there is also the fact that XP is much lighter than his successors.
I can install XP on a VM and get away with a few GBs of space; the last time I tried Windows 7 instead, the space occupied started to grow uncontrollably, even after making little changes.
With XP ending support, I see many corporate customers switching to ReactOS. Firstly it's free rather than paying for a Windows upgrade, and secondly the premise is that all your apps will keep working exactly the same way, so no compatibility problems, and hence hopefully little to no downtime.
To think that businesses will latch on to a solution that has never left alpha stage for development is shortsighted at best. There are far better solutions for making your XP applications continue to operate on modern systems.
Or what we will see instead is the status quo support or not from Microsoft. There are plenty of 9x machines out there.
I don't. However, Wine on Linux is plenty up to running quite a lot of software for production use (I have personal experience of this) and is IMO generally worth a try if you don't want to set up a gratuitous Windows VM.
Having an elevator-pitch somewhere obvious where an idiot like me could see/find it would have been nice. They really could have put 'awesome' in 15 different fonts and sizes, and maybe some 'more awesome' in there and it would have told me just as much.
I'll save everyone the wikipedia jump: This is intended to be binary-compatible with windows NT-based applications.
Wow, now if these guys could magically continue support for WinXP, they would become filthy rich!
Of course this is not possible, since it would entail uninstalling all current XP machines and installing ReactOS and hoping that ReactOS == WinXP
You could still maintain a level of compatibility for some critical enterprise apps, and ReactOS could provide enterprise services for specific apps.
Anyway,there is no silver bullets or easy solution to the XP migration problem,especially critical apps that relies on IE<=8 depreceated features. Does ReactOS runs IE by the way?
ReactOS is an open source reimplementation of Windows NT series operating system (e.g. Win 2003 Server, 7, 2008). Similar to Linux started as an reimplementation of Unix.
ReactOS has binary compatible with Windows. This allow your Windows applications and drivers to run as they would on your Windows system. Additionally, the look and feel of the Windows operating system is used (Win95 classic style and WinXP theme support).
ReactOS is still in development, but a lot of Windows apps and some several types of hardware drivers work fine or with minor glitches.
Gosh I remember that theme! Don't forget the "Island Man" [0] screensaver, Johnny Castaway. We used to spend hours watching him and his antics back in the day. I miss the whimsy of yore.
It's simply not suitable for real-world usage, and actually, not suitable for anything more than installing it in a virtual machine, playing with it for fun, and destroying the VM. The "alpha"ness of ReactOS is not the same concept of, say, Ubuntu.
Sad, but true. It needs a huge amount of work; compatibility matter little - if one needs compatibility for a given up, wine is a much more usable choice.
If one really needs XP compatiblity, I think an XP in a virtual machine without networking is going to be the workaround for a very long time.
Well, they don't "work together" - Wine devs avoid ReactOS code and devs like the plague. However, Wine is happy for ReactOS to use their DLLs - so Wine does Win32 and ReactOS does the lower, weirder layers that Wine doesn't bother with.
Copyright worries, I believe. Wine is paranoid of contributors who may have looked too closely at Windows or reverse-engineered it in potentially risky ways. I am vague on details.
Also, Wine is LGPL and ReactOS is GPL, so no code can flow in that direction.
Being under active development doesn't mean that ReactOS is secure. Sure, there's attention being paid to OS-level security policies (user accounts, passwords, etc.) but there's nowhere near enough dev resources to focus on the kind of vulnerabilities that are actually exploited against win32 systems (ie. bugs).
Running a Windows firewall and virus scanner might help, but a) do they run reliably (they certainly hook into the OS more than most standard apps) and b) how many exploits will be ReacOS-specific?
That's an interesting question: Is ReactOS even vulnerable to win32 exploits? In other words, are the vulnerabilities flaws in design, or flaws in implementation? (Or some of each?)
This appears to be a pure marketing site aimed at getting IndieGoGo donations. Nothing really new to see here if you've looked at ReactOS in the past (no, 0.4 isn't out yet).
I think the project is worthy of marketing. Nothing wrong with trying to get some jake together to speed development if that's what they're trying to do. Full time developers should be working on this effort.
Hah my first thought seeing screenshots was "oh, looks like windows 95" :D but the page was more about "joining a revolution" than giving me actual information
