![]() That all being said, if there was sufficient interest, I'd say 2 years to get to 1.0.0. If they don't have the resources to finish an OS in 24 years, they sure as hell don't have the resources to fight a legal battle with a tech giant.įinally I imagine that virtualization will progress to the point where one could run older Windows software in an emulation container or virtual machine container on whatever operating system (probably Linux) with little effort. ![]() The legal process alone would likely shut them down. It doesn't matter if Microsoft is in the right. I don't think "it runs old Wndows programs" is enough of a unifying principle.Īdditionally seeing how it's already been over two decades since work started on it I imagine the developers will die before they can finish their work.įurthermore at any moment Microsoft could cease and desist them and they're dead. I think a lot of it has to do with the general hostility of the open source community towards Windows and "hur dur we have GNU/Linux."Įven if it does reach 1.0.0 I'm afraid long before it will fracture like the Linux community and just be a general mess of distros and incompatibilities. But I don't think there's enough interest in the platform for it to ever get off the ground. I hate to be a nay sayer here, especially since I want to see this happen. ReactOS will hopefully be production-ready for the risk tolerable by enterprises before this aforementioned decision point. Some Windows-based applications internal to companies will move to web-based systems running on Linux or a modern Windows. If it's cheaper over a period of time, say 20 years, to replace or modify the application, then that's the way to go. If that cost is less than the cost of replacing or modifying the application, then it's worth pursuing. That's the gambit of ReactOS: a new OS with new drivers that looks to the framework and application like the old OS. If you get new hardware, the old OS might not have drivers for the new hardware. ReactOS operates on the assumption that it will be cheaper to replace the underlying operating system as an abstraction on top of modern hardware than it will be to change the software. It remains to be seen what the actual economics are here. It'll become more relevant has the hardware running legacy Windows OSes dies and applications cannot be cheaply ported to the newer Windows OSes. All these factors contribute to the impact of ReactOS state if it deserves the Beta release-state. For ReactOS to reach Beta (0.5.0) phase you have to take into account the stability, compatibility and reliability of the Operating System. ReactOS, as part of the FOSS ecosystem, re-uses and collaborates with many other FOSS projects, most notably the Wine project, which presents a Windows compatibility layer for Unix-like operating systems.Years, maybe even a decade or more, unless someone with money comes along and funds development significantly. When ReactOS reaches 0.4.9 version it'll pass to 0.4.10 and so forth. ![]() The project partially implements Windows API functionality and has been ported to the AMD64 processor architecture. ReactOS is primarily written in C, with some elements, such as ReactOS File Explorer, written in C++. However, many Windows applications are working, such as Adobe Reader 9.3, GIMP 2.6, and LibreOffice 5.4. As of February 2022, it is still considered feature-incomplete alpha software, and is therefore recommended by the developers only for evaluation and testing purposes. ReactOS has been in development since 1996. Hybrid (designed to be compatible with Windows NT family)Ĭlose ▲ ReactOS 0.4.14 running the Firefox Web browser CD-ROM ISO image, QEMU image, VirtualBox image, VMware image, or source code
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |