1. 7

complete changelog

  1.  

  2. 1

    Hm. Still no browser or installer in the live CD, and installation to disk ends up in a blank screen with no explorer. I used to be able to get it to crash at least… Let’s give them a few more years.

    1. 3

      The greatest burden and blessing of ReactOS is that they’re trying to emulate a specific, existing operating system. It’s a blessing because they have a reference implementation against which they can test. It’s a burden because its a Sisyphean effort of playing catch-up with something that took years and millions of dollars to write.

      Part of me wishes they’d strip everything out of the OS that deals with multiuser support or drivers, and create an OS much like IBM’s CMS in spirit: a single-user operating system that runs on top of Xen or KVM or something, letting the lower-level OS deal with the more fundamental aspects, and focuses entirely on the user layer.

      If I had unlimited free time, that’s what I’d do with Haiku…

      1. 3

        focuses entirely on the user layer

        You mean like Wine? Linux + Wine has better compatibility than ReactOS, IIRC.

        1. 2

          A big problem of ReactOS is that they’re chasing features instead of stability, and that is to a large extent caused by the developers' natural motivation. In other words, they don’t need to play catch-up but they might want to pick a specific operating system. :) If only they’d make the Windows 95 subset work well, then this star would shine a lot brighter (yes, I know, ROS is NT). The releases so far have always been severely undertested and full of variously crippling issues.

        2. 1

          Hey, at least it isn’t written in javascript, in spite of the name.

          1. 5

            ReactOS predates that javascript framework by well over a decade. Blame the proliferation of js frameworks for the name collision, not the poor ReactOS devs.

            1. 1

              I know, that was supposed to be a joke ;)