4 ms·
why bother following the clearly failed model? ReactOS has been there for more than 20 years, how many people are actually running ReactOS in production?
by dis-sys 6y ago
why bother following the clearly failed model? ReactOS has been there for more than 20 years, how many people are actually running ReactOS in production?
- paulryanrogers 6y agoReactOS got too ambitious IMO. If they had stopped chasing versions at say XP/2003 then it may have matured more quickly. That said they are getting closer to useable with every release. Like FreeDOS before it I suspect it will fill a niche where Microsoft binaries are too expensive yet compatibility is important.
- detaro 6y ago... but they are targeting XP/2003?
- jeroenhd 6y agoIf they stopped at 2003/XP then no modern web browser would run on it and the system would be even more useless than it is today. If you want any decent usage out of the system, you need to support a whole bunch of APIs from at least Windows 7 (probably even Windows 8 now that 7 is our of support) because people have stopped compiling for XP ages ago.
- paulryanrogers 6y agoLooks like they are open to implementing newer APIs in the future. So if the version reported can be spoofed or modern browsers only feature sniff then there is hope.
- JdeBP 6y agoNot targetting versions beyond XP is what ReactOS does, and pretty much always has to my knowledge. It's explicitly mentioned in its doco that it targets Windows NT 5.2. Indeed, this is the first thing dealt with in the ReactOS FAQ on its wiki. * https://reactos.org/wiki/ReactOS_FAQ https://reactos.org/wiki/ReactOS_FAQ I found this disappointing at the time that ReactOS was announced, as I recall, because there were a few things that were architected better in Windows NT 6.
- paulryanrogers 6y agoThanks for pointing this out. My recollection was inaccurate.