https://news.ycombinator.com/item?id=34426198
(204 points/4 months ago/129 comments)
The ReactOS project, although currently focused on Windows Server 2003 compatibility, is always keeping an eye toward compatibility with Windows Vista and future Windows NT releases."
I always felt that they should have focused on one, probably Windows XP, and tried for almost 100% compatibility, rather than moving the target toward later releases.
If it wants to remain relevant, it'll need SOME Windows 7 APIs at least. It doesn't need full compatibility like I think it should with older releases, but it needs to be compatible enough to run a few nice to haves as well.
Mind you it's a mess of various browsers and versions and modified ones and patches to the modified ones, but if you are interested, here is a good entry point to the rabbit hole:
https://msfn.org/board/forum/201-browsers-working-on-older-n...
But isn't that what they are doing by focusing on 2003 (which is almost the same as XP)?
I thought the kernel aspects would be interesting, but they were really trying for driver-level compatibility with Windows NT, which means that they have to have essentially the same operating principles, etc. For some reason, I didn't want to make a line-for-line clone of Windows itself. After all, OSS people are always talking about how we would do it better.
If the goal is to be able to use the proprietary drivers supplied with some kind of hardware on a mostly OSS base, that's a decent goal. But if you want to be able to run it with complicated software that uses a lot of Windows APIs, etc., it's a fools errand.
However, I found it interesting how ReactOS could be used to teach Microsoft devs about Windows internals, even if it wasn't exactly the same. That sort of blew my mind. When you have a bunch of trade secrets, you don't really want the whole company to have access to the code, I guess, and so you benefit from having an open source clone to point to when you want to say how something like a Mutex is really implemented.
I don't believe they're competing against Microsoft.
Gaining compatibility is as much a cooperation from ReactOS'es side.
But it's a losing battle to gain compatibility with Microsoft, because it's against Microsoft's ethos.
I admire the people behind ReactOS for their perseverance, I really wish I had just 1/10th of what they have.
Really? Are you absolutely sure, Sherlock? Did you know that the water is wet already or are you going to announce that in your next comment? ;)
The project has many other reasons-to-be and it would probably be very hard to find anyone seriously believing that "competing against Microsoft" is one of them.
I don't thinks it will be one day...
https://askubuntu.com/questions/32499/migrate-from-a-virtual...
https://reactos.org/getbuilds/
https://iso.reactos.org/livecd/
Though I would agree with the sentiment that the project needs to speed it up to reach a point of greater usability or needs more help in doing so, to remain relevant and be seen as a viable alternative.
Otherwise it is either Windows, or Wine on some flavour of Linux.
But I still have to rely on running real Windows 7 as a VirtualBox guest to run my HP MFP Scanner Software about 10 times a year.
I have really wished for Wine to support recent releases of Microsoft Office.
As a matter of fact, I think it is a shame that so few support ReactOS. The idea is grand and think about how many resources people are willing to invest into using, say, Linux as an alternative to Windows (I love Linux, by the way): If those resources were spent on ReactOS, the project would be flying in 5-10 years or so. Then we could perhaps have a well-designed, compatible, free "Windows".