this post was submitted on 04 Feb 2024
110 points (100.0% liked)
Technology
37742 readers
484 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Sounds cool, though I'm a bit confused as to why that is such a big priority given that ReactOS currently aims to replicate Windows NT 5.2 (XP x64 / Server 2003), which did not provide graphical set-up*...
* Technically all Windows versions up until, IIRC, Vista had their install process in two stages: a text-based stage where you'd input the most basic info (what filesystem to install onto, what Windows directory to use, etc.) and a graphical stage once the basic files are installed (where you'd be asked what devices the computer has, whether it's networked, date/time, etc.). From Vista to the present day, the first stage is graphical as well. ReactOS' latest release uses the pre-Vista model, but the latest blog posts indicate a move to the more modern one.
Why do you think aiming for NT 5.2 compatibility should preclude them from building a modern GUI-based installer?