![]() There was also number 5 - opportunity to get your code signed with ReactOS code signing certificate. So why this project still need some attention and support? Just a few small reasons why it still need to exist.ġ) Wine as they share part of code base, including patches Ģ) Good laugh when sometimes you are trying to use this OS ģ) Variability and opportunity to experiment with Windows like code for beginners and noobs Ĥ) It is free and doesn't demand anything in exchange of it existence. If you want to learn something - use original Windows source as case of study. Students learning project? Maybe, but better not to learn anything from it as ReactOS is a perfect example of deep failure in design, positioning and implementation. What is ReactOS today? Windows replacement - no and never will be. ![]() When you start doing something - it will crash and highly likely reinstall will be the only option after. It is end of 2018 now and ReactOS is barely "stable" to install in virtual machine, start and do nothing. Impossible to work and completely out-dated, uni-processor x86-32 configuration, bugged as hell failed Windows clone running on FAT32 (with broken/incomplete fs driver), clone which barely can support few devices in popular virtual machines. Since it was considered as "alternative" on government level, that probably mean this product is ready for something, then I tried it again. Or probably this was a main goal, because entire idea and competitors were merely a joke ) Fortunately they didn't manage to go through. Since this was obviously low quality product at that time (and currently too - nothing changed) if they win it mean waste of Russian government budget funds. So ReactOS was considered as candidate for client OS for replacing MS Windows products. “Creating an open source operating system based on ReactOS for PCs, laptops and other mobile devices”, “Creating an open source operating system based on ReactOS for servers”. This time it was evaluation of projects on import substitution infrastructure software. ReactOS was still alive and still in alpha where "it can but not today". Next encounter was almost ten years after in 2015 year. Ok, but there is no Windows code in ReactOS. Microsoft code wasn't that extremelly good and they managed to make it even worse. However I still encountered it pieces of source on various forums etc which actually was total frustration and failure because ReactOS developers in attempt to hide their copy-paste parts turned code into ridicuolus mess of trash. Approximately at the same time access to actual Windows code was acquired and ReactOS have lost any value for me. It wasn't ready for anything even for virtual machine installation. In 2006 on a first hype train about this "Windows replacement" OS I tried it. ![]() For that time it was probably one of the best sources for this kind of queries. Prologue If you don't want to read all this bullshit - skip and go to ROCALL chapter.įirst time I encountered ReactOS in 2004 year when I was looking for declaration and definitions to the Windows Native API missing in Nebbett book. ![]() There was never such an accusation in the first place. Imagine running your favorite Windows applications and drivers in an open-source environment you can trust. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |