Hell, I have never seen a ReactOS installation in the wild, and I'm the kind of person whose friends install Haiku, Nix and NetBSD as their daily drivers. And the second-hand stories I've heard about people who did install React was basically "I was bored, I put it on a drive, played around for 5 minutes, and wiped it."
But that doesn't discourage them. Meanwhile, work keeps going on in the background. So many untold man-hours of thankless work going into the project, and the vast majority of that "hard" work with no payoff for years.
And now it's finally getting close to actual Windows, after decades of work, and soon (well, years, but still) people will be using it everywhere as a replacement for Windows.
This is one of the most important software projects in history. My hat is off to the ReactOS developers, and congratulations on the latest release.
 Here are the names of the 75 programmers that have worked on ReactOS: https://github.com/reactos/reactos/blob/master/CREDITS
No they won't. It's a fringe OS that requires technical expertise to install. Not only that but it looks like "old Windows". Users won't want to work with a Windows from a decade ago. Not only that but it'll have bugs and no support.
You'll see tiny pockets of people using it but as Microsoft gets closer and closer to simply having a free OS it doesn't seem likely anyone would ever use this OS for anything beyond "hey, that's cool!".
Depending on the age group, I guess. I know plenty of people who would say that Windows had its peak usability around Windows 2000/2003 and only got heavier and more confusing later on.
If I know that ReactOS had a good chance of running most regular Windows applications, I'd install it on my mother's laptop in a heartbeat, and she would love to see the familiar, lightweight OS.
Frankly I can't think of anything they've added since 2000 to windows (except better security) that was an improvement.
I occasionally have to use Windows for work and I really hate Windows 10, it's just a chore to deal with when you only boot it every couple of weeks just on the updates.
I think the 'seniors' amongst us may well welcome ReactOS together with those in small companies who run legacy industrial hardware from Windows PCs (depending on stability &c).
Given Microsoft's mostly successful effort to make Windows more friendly to the user, I find it hard to believe any of these people have extensive experience with Windows 7+
I find that Windows 2000 has the best support for keyboard users among GUIs. Better that MacOS, better than all the incarnations of Gnome/KDE, better that the following releases of Windows, that "forgot" about the keyboard and focused on other input systems.
You can see that in many small things, like sane keybindings and reasonable sequence for selection through tabs (for example, going from the path bar on the top to the folder content requires two tabs in Windows 2000 but four in Windows 7, unless one does some find tuninng of the UI).
The "mostly successful efforts" you speak of seem to have been focused on delivering ads, TOS-backed spyware and those weird Metro apps. The result is certainly simpler from a strictly visual standpoint, but more usable is something that I wouldn't be too willing to concede without some data (and I don't mean install data/user base, given how Microsoft's customers don't have much of a choice in this department). Frankly, I don't see how the weird start menu or having both the Control Panel and some weird Settings thing help with usability, but UX is a surprising field, I guess.
That's fixable (and not different from Windows).
> Not only that but it looks like "old Windows"
That is by far the easiest fix of all. People just care more about making things work right now.
Plus, a lot of people actually preferred the older style.
> Not only that but it'll have bugs
Welcome to software. Windows is also full of bugs.
> You'll see tiny pockets of people using it but as Microsoft gets closer and closer to simply having a free OS it doesn't seem likely anyone would ever use this OS for anything beyond "hey, that's cool!".
I think it might end up being quite big quite soon: There's a bunch of proprietary software out there that is old, and not Windows 10 compatible.
Things like car diagnostics software. If ReactOS gives them a way to get things working without Win10, I'm sure they'd eat it right up.
ReactOS just isn't ready for that yet. It's still major version 0.
Eventually, they'll have to (DirectX 12, but I'm sure there's a ton of APIs for non-games as well and drivers will stop being updated for Win7).
But if ReactOS can reach a level of maturity and compatibility to please such people, there's a sizeable niche there of people who:
1. won't switch away from Windows to Linux or BSD,
2. but would be willing to adopt a familiar and compatible operating system.
- Then it looks like this.
- And still flows nicely.
Unfortunately, last time I looked audio software and drivers weren't well supported on ReactOS. If I could get Reaper, my audio interface and commercial VSTs running on it, I'd ditch Windows forever.
To reach any mass of users (outside of turnkey solutions where the end users may not know or care), you need commercial support and the later needs concrete identified market segments. To parallel Wine - ROS needs its own CrossOver (but not Cedega).
Of course, the network driver didn't work, sadly :(
Not convinced that's a weakness as opposed to a strength. Every time Microsoft changes literally anything about their UI, they alienate a legion of people who suddenly feel their workflow and productivity has been irretrievably broken.
Windows will never be free os, you will pay heavly with your privacy and from what I have seen on GUI changes, they are more moving into direction of cloud (minimal installation on pc, the PAID resources on cloud) than beeing free.
ReactOS devs, good work and thank you, I hope I will be able to use it in the future.
I don't agree. Vista was a mess but they seem to have made such tight performance budgets for 7, 8 and 10 that any computer which can run the 11-year-old Vista can also run 10.
There has been a lot of good work done on the underlying system, but it's had a ton of useless buggy crap piled on top of it.
(I will refrain from further commenting as my technical perspective is hitting into large fanbase of both systems and karma here is really not beeing able to handle it. At the end it is the terror of the less technical average.)
Here’s more info: https://scissortools.wordpress.com/2011/11/23/more-on-window...
But if ReactOS can be practically comparable - it can get some traction too.
Free OS? Even bog standard windows 10 pro (non-oem) is hardly free. Never mind a datacenter server license (aka you need to run 10s of instances in vms in order to get anything line useful utilisation from this modern server).
>It lights a fire under M$'s asses to make windows competitive
>Adoption is slow but exponential. Today is the first day I learned about ReactOS and I'm excited. I can program and I have money. If people can find value in it, adoption will grow.
Err... no. Not unless the installed base reaches a critical mass. And certainly not when the market share is not even 0.1%. macOS (or even desktop Linux) has a higher installed base and they don’t bother Microsoft significantly.
I’d be more optimistic if the OS had not been around for two decades. It had its chance when the likes of Vista was released. If it didn’t make a dent back then, it is not going to make one now - especially since Windows is at its best in terms of usability. Sure there are concerns about privacy, but those didn’t prevent Google from acquiring a (almost) monopoly in mobile market. Microsoft’s own attempts went nowhere — and they have infinitely deeper pockets compared to people behind ReactOS.
And even if it does gain momentum, I am fairly sure that Microsoft will find a a way to sue them into oblivion.
Except for they did. I'm pretty sure WSL was about developers who had preferred GNU/Linux-based systems (or macOS, since it can be compatible for some cases) for work, not about just running some *nix server software on Windows machines.
After seeing that I really want to save up and buy only Macs from now on.
Did Linux succeed because other UNIXes were bad?
In my opinion, the reason why we need ReactOS is independent from whether Windows 10 is good or not.
And yeah, I agree besides the privacy issues, Win 10 is pretty good
No, it succeeded because there was a need for a UNIX like OS not encumbered by lawsuits (like BSDs) or costing a fortune (Solaris, SGI etc.).
Linux is a clean room implementation that doesn’t borrow any code from proprietary AT&T UNIX, ensuring that it has future. That, and the backing of FSF means it is not going to be sued into oblivion - something that could not be said for BSDs and other free variants back in 1990s. No one wants to invest into a something that may be shut down anytime. It is the fighting thtpat hurt the BSDs the most — causing them to be overshadowed by Linux despite being superior in many ways back in the days. Some would argue that they are still technologically superior in certain areas — but that is debatable.
And on the desktop it took a backseat to MacOS for similar reasons.
> This Windows 10 Setup Script turns off a bunch of unnecessary Windows 10 telemetery, bloatware, & privacy things. Not guaranteed to catch everything. Review and tweak before running. Reboot after running. Scripts for reversing are included and commented.
I recently updated to the "Creators Update" and couldn't believe the amount of shit that popped up after the install asking me pointless questions, trying to integrate with things, trying to get me to activate OneDrive etc.
It's not just post-install either, this stuff pops up when you're in the middle of something else!
The thing I like most about Gnome is how it just stays out of the way. I don't use my OS, I use the applications I have installed. The shell should provide an optimal environment for them to run in and an easy way to launch them - and nothing else.
Don't get me wrong, I've been a fan of Windows for a long time and 10 is the best version for years, but the popular Linux distros and macOS seem to do a better job of staying out of the way of the user.
I think Microsoft are losing track with all the "value added" stuff they're constantly trying to foist on people - and don't even get me started on the tracking.
It's not especially common, but I do know of a couple kiosks and a PoS system that run ReactOS under the hood to avoid Windows licensing.
This is a pretty good system, because the terminals are able to be updated really easily. A lot of cafes and stuff also use iPad POS software (one called 'Vend' is really popular here) and it doesn't have to be certified. This is part of the reason that it took hardly any time for almost everywhere to support contactless six or seven years ago. For example at Myer the POS systems look 15 years old but the attached card terminals are usually only a year or so old.
As for the terminals on older PoS as long as the PED is certified and the PoS is certitied its not a problem.
Both very small Australian companies, probably about 100k deployments between them.
I've seen it once so far, because my employer has a no Windows policy for contractual / security reasons and I was requested to translate a foreign-language dialog (on an English language OS installation). It was to solve / use an esoteric bit of Windows, that ultimately did not succeed. I commend the effort to make such a distro, but it is still a decade or longer away from the "casual" techie.
I understand that ReactOS doesn't require Linux as a dependency, but is that a significant win?
ReactOS does replicate the NT Kernel, so in theory (if it ever gets there), ReactOS would be able to run Windows Drivers. IE: the "real" NVidia and AMD Drivers or any other kernel-level drivers that exist in Windows land.
These days, AMD (and even NVidia) have decent Linux drivers. And WiFi drivers have Windows->Linux translators as well. But full compatibility to any Windows binary (including device drivers) is certainly a noble goal. There are a lot of little hardware devices that are written for Windows only (ie: specialized medical equipment, CAM / CNC Mill programs, etc. etc.) ReactOS would allow a smooth transition to Open Source if they achieve their goals.
It should be noted that there are a ton of Windows OS-level details that Microsoft does much better than Linux too. IE: I'd argue that Microsoft's security model (SIDs + ACLs) is superior to Unix-style Users + Groups. A large group of open-source developers who strongly understand the low-level internals of Windows is certainly a good thing in any case.
Even then, ACLs are just part of the picture. Windows NT's "SID" system for identifying user permissions is far more flexible than users / groups.
WinVista and later also adds mandatory access control on top of that, in particular event logging / auditing guaranteed by the kernel and "integrity levels". Anything that is "drive by downloaded" by Chrome for example has an integrity level of "untrusted" and thus is locked out of all kernel objects. (IE: "untrusted" integrity in Windows prevents access to files, processes, threads, mmaps, all services, etc. etc.).
Linux's security model is too weak to be used in a modern operating system. That's why Google extended it with all of the Android App stuff. Android's security model is closer to what modern Windows can do.
And if you know anything about Android (despite being built on top of Linux), its security model is quite different. Windows basically offers Android-level security at the kernel level. (maybe a bit more: major services on Windows, such as LSASS aka Login / Password service, can run in an isolated VM for example)
But I can see an obvious use case - testing. Customer reports an error but you can't reproduce it on your company's Windows development machines. I was able to reproduce a couple of bugs that way with wine and I imagine it could be handy running under ReactOS.
* I've only ever tried it in a VM.
Ubuntu server with LAMP is the greatest thing of all time, but desktop Linux has disappointed me over the nuances like mouse acceleration settings, netflix not working natively, etc...
Since it barely works at all.
I'm not sure what issues you've had with your mouse in the past, but in the vast majority of cases it works out of the box. I can say that desktop Linux has come a VERY long way in the last 3-5 years.
1. Reboot the computer in DOS mode.
2. Change to Windows directory.
3. Delete the .pwl file for a user.
4. Reboot back into Windows 95.
5. Enter a new password in what was once a login screen asking for the old one.
Simpler times for hackers back then. :)
Anything trying to be compatible with a large, greedy company's software is a huge risk if it starts cutting into their profits. Maybe nothing will happen but something might happen. I'm more concerned for companies like EnterpriseDB than FOSS projects like ReactOS, though. The lawyers do prioritize on those making money with the competing software.
I wouldn't be surprised if we open-sourced NT, at the rate things are going. Windows devs are likely flattered by ReactOS at this point.
> Even if they abandon the project it's open source and work can continue even after MS has their way with them.
Such infringement claims are damaging to the legitimacy of the codebase itself. Anyone taking up the project could face the same problems.
Security probably hasn't been tested very much but it probably will be as secure as most other OSes? (i.e., not very secure)
1. You can't use the OEM license with retail installation media.
2. You don't get OEM installation media because the license is tied to the hardware.
3. The OEM recovery media can't be restored to different hardware.
4. The OEM license key can't be used to install a retail Windows install on a different computer.
I've done it once in the past and it wasn't super complicated. It looks like it might be harder to find the oembios files now, but I bet you can still accomplish this if you're determined.
https://superuser.com/questions/539714/windows-all-oem-activ... has some details that could get your pointed in the right direction
Now that's a name I've not heard in a long time...
Microsoft held back the netbook market by setting strict requirements on the tech specs required for Windows licencing, without that restriction I'd suggest we'd still have a healthy market for netbooks today.
> ""Our license tells you what a netbook is," said Ballmer at the Microsoft-hosted day with Wall Street analysts. "Our license says it's got to have a super-small screen, which means it probably has a super-small keyboard, and it has to have a certain processor and blah, blah, blah, blah, blah.""
> "Last May, the Malaysian Web site TechARP.com, which regularly leaks information provided to computer makers by Microsoft, reported that the company would restrict Starter to specific netbook configurations. According to TechARP, Microsoft will only sell Starter to OEMs for use on netbooks that have a 10.2-in. or smaller screen, no more than 1GB of memory, a hard disk drive of 250GB or less (or a solid-state drive no larger than 64GB) and a single-core processor no faster than 2GHz."
Honestly, just grab a Raspberry Pi for your retro gaming console. It almost certainly does the job better, and the power usage difference will pay for itself soon enough.
"security" isn't a big deal either, just keep all your ports closed and don't run untrusted code or unnecessary services. AFAIK all the exploits have been on services and such, which shouldn't be exposed to the Internet anyway.
IE: Win10 can run the password manager service on a separate VM now automatically. Hell, you can start new version of Microsoft Edge in a clean and isolated VM, requiring the attacker to use a hypervisor zero-day to pwn your box. And since the Microsoft Hyper-V hypervisor is often running through UEFI secure boot with assistance of the TPM modules on the motherboard, and because the Hypervisor has very few services running (really: any service is in its own VM), its a much, much harder attack surface to go through.
Security features that add convenience (ie: group policy allows admins to automatically open websites in "Application Guard" mode) helps a lot. When the user literally only has to wait ~5 to ~10 seconds to boot up a clean version of IE isolated inside of a VM (separated in a RDP session), its much easier to have widespread security throughout a network.
I mean really: think about the security model needed to pwn AppGuard + IE. You either need to pwn the RDP session (unlikely, but hey its possible). Or, you figure out how to escape an isolated VM, when said VM has virtually all applications locked out. I saw a security demo of AppGuard recently. You can't run cmd.exe, you can't run powershell, you have zero permissions inside of your VM. If you somehow escape the sandbox, you STILL have to break through a hypervisor to get to the user.
Its way, way WAY easier to do "proper security" with Win10 + all of the virtualization tricks (AppGuard, Credential Guard, Device Guard). The modern Win10 security model is beginning to be immune to even kernel-mode exploits.
With that being said: WinXP has security problems with modern Win Vista+ because that's the edition where Microsoft decided that direct-hardware access is a BAD IDEA for standard usermode applications.
WinXP allows any user-mode application to directly talk with the hardware. Win Vista+ does NOT allow it. And that broke a ton of programs (old controller hardware, printer drivers, etc. etc.)
Fixing security issues causes compatibility problems.
What if we could go back and access that infrastructure, what lessons could we learn?
I really dont know, but I personally see this as useful from an entertainment POV, let alone function.
It gives a huge, deep history lesson from author's perspective covering important events, hardware/software, and especially the culture. It was fascinating. Also made me hold off on MorphOS for one of my projects.
> "The problem was that OS wasn’t completely prepared for that, but clever people from Phase5 found a way - they made their own microkernel (called PowerUP, later WarpUP)"
PowerUP and WarpUP were competitors, and were the seeds for the later Red vs. Blue civil war.
If you'd like a clearer history of the Amiga, I'd recommend this series of articles on Ars Technica (it doesn't mention AROS, but is otherwise a good introduction):
The best option they suggest is moving it to a VM under Windows 10's Hyper-V:
If anything ReactOS picking up those small companies is beneficial to MS by keeping them in the MS ecosystem.
Maybe the 2020 win7 end of life would be a good time to do something like this. I don’t know if there is a good enough financial reason for MS, but from a user’s perspective I think it would be better than the situation today.
This is an impressive update when most projects, and not necessarily wrongly, always move in the opposite direction. Good to see.
As a free Unix user I'm primarily interested in ReactOS in order to test certain Windows things such as cwrsync over ssh. I tried installing ReactOS about a month ago but didn't have the right hardware to make it through the installer. I will definitely try again.
I have been keeping an eye on Reactos for over 10 years, it is still a promising candidate for my legacy systems, USB Install would still be good to have as it is painfully hard to get it on to newer systems which don't have Optical drives.
It took me a while but I can now compile my gui applications for Linux, so going forward that is my strategy, but lots of factories out there still scared to move off windows XP and Reactos would be ideal.
This does actually ring a bell for me - I seem to remember mention of it very early in the century. That perhaps cuts to the heart of the issue: it's been going as a project since 1996, yet it's still only considered alpha. In other words, I'm not so sure it's going anywhere fast, and I'm not sure what you'd really use it for.
ReactOS is a usable Windows NT 6+ clone, with kernel ABI ( driver ) compat, that runs real software. What are you comparing it to, to be able to qualify the speed of its development?
Don't be sure about something in the tech on such a long time frame. Just to put things into context. Andoird is less than 10 years old and already close to windows market share territory. Facebook is only 14 years old.
I can't even imagine to comprehend what will happen 20 years from now.
JQuery is 11 years old now. ReactOS is a goal and nothing more. Nobody is using it right now because it's barely usable outside of a VM, and even then it's software compatibility is smaller than WINE, let alone Windows.
ReactOS is a cool project, but your comments are bordering on delusional.
10 years ago there were 0. The churn in JS code is just too high.
2. Oracle v Google still isn't over, so even drawing any inferences about Oracle v Google itself would be premature.
3. The copyright holder here is MS. Any action on their part to go after ReactOS now be the undoing of all the goodwill they've built in the Nadella/MS-on-GitHub era. The result would be (a) a bunch of I-told-you-sos from the leery folks still holding on to their grudges today, and (b) a massive, massive, innoculating "fool me once…" reaction among the folks who'd actually been made suckers for not heeding the grudgeholders' warnings. All in all, it would be a spectacularly bad idea for MS at this point, especially given how much weaker their empire has already gotten in the last decade.
> Talking about the notification tray, due to Ged’s work, icons of killed and finished process are now automatically removed, even when apps crash. This is something that Windows doesn't even provide with Win10, and many Windows users may have noticed.
Made me chuckle. This has bothered me since forever. It seemed like such a low hanging fruit to fix, I wonder why Microsoft never did.
I'm assuming it's because of the size of the codebase, available engineering resources, return-on-investment calculation, and a business prioritization of new features over refinement.
Most engineers can look at their own work or codebase and think, "well, that's a bit shit but it works well enough." I can't imagine their backlog. I'm sure it's lurking in an issue queue somewhere.
ReactOS, another guess here, does either a polling check if all taskbar icons have valid process handles or a check whenever a process exits.
Explorer can’t tell if the app connected to an icon crashed without polling or other tricks which Microsoft probably wants to avoid. But it can tell if you move the mouse over them and it can’t send the messages to the application.
Also the notification area with a million icons is bad UI that I can imagine Microsoft not wanting to invest in. They tried to discourage its use by hiding most of the icons all the time.
Having worked at large corporations (not Microsoft) before, I can definitely see how things like this happen --- and the reason why "enterprise" software tends to have a lot of these superficially simple and annoying defects. To add insult to injury, the codebase is often offensively overengineered and in precisely the wrong direction to facilitate the change required to fix such bugs, and even the tiniest of changes requires a ton of extra paperwork, approvals, and reviews.
I hope it was an outlier event and that external contributions are better audited today.
https://www.reactos.org/wiki/WINE explains a bit but still doesn't answer the question.
P.S. oh by the way, the developers of both projects are apparently collaborating and ReactOS uses Wine's DLLs for their userspace, so my question is not meant to criticise the "double-effort" or anything like that.
There are also some technical advantages for applications that require driver code. Examples include specialized software with intrusive DRM (where either the DRM is so beastly or interest in the software is so narrow that there's no crack; ISTR that Cubase is sort of legendary for this) or software that drives industrial equipment. Wine will probably never run this sort of thing.
https://wiki.winehq.org/Wine_History and https://www.reactos.org/wiki/ReactOS/History were interesting to look through.
I tried wine-develolment a few days ago and 3D performance is still rather spotty (amongst all the other usuall hiccups). That being said is has helped me play a few games with a decent experience.
It’s been useful to be able to run the same Ubuntu and SUSE images as VMs and servers do, but that’s only really possible because the built kernels have RPi3 support (but at least you now don’t need a custom image with U-Boot).
As a random person stumbling upon this, what value would you assign to it? What could you imagine the end goal to be?
First of all, no driver for the network card in Virtualbox, though Vmware worked fine.
Second, no web browser...
Third, the mouse sometimes freaked out and got stuck in a corner.
If you meant lack of default browser preinstalled though, I agree with you its lacking.
It's necessary to change the network card in VirtualBox for internet connection to work IIRC.
I'll take another look.
If you install 7Zip, you should know that 7Zip does not associate itself with file extensions by default. This is 7zip behavior. You need to run 7zip, go to options, and set associations by clicking on the '+' button.
Currently, the supported graphics drivers is pretty sad for modern-ish hardware on ReactOS, because they are limited to drivers for Windows Server 2003 / Windows XP, which aren't available for a lot of modern cards (or integrated chips, for that matter). Additionally, a lot of the older XP drivers don't work well on ReactOS today.
Do you mean faster?
The best way it seems to check the AppDB is to do something like
site:https://appdb.winehq.org "c&c" "red alert" "2"
- Version 1.1b (retail): Copy a DLL over for working sound, then everything works: https://appdb.winehq.org/objectManager.php?sClass=version&iI...
I think looking at MS documentation is okay. You're allowed to look at MSDN for Wine development. Since the projects share code, you're probably allowed to do so for ReactOS as well.
Also just a side note, Linux isn't exactly a UNIX fork either. Linux was developed from scratch on a MINIX host, which in turn was another OS designed to be UNIX-compatible but did not actually use any UNIX code. To put it another way, it's Unix-like two generations removed, but definitely not something you could call a fork. That might seem like a small detail to you but SCO vs IBM says otherwise.
- You need to fix your flaccid dev community. Your forums have a terrible S/N ratio. IRC may be great and all, but I don't see any hard documentation behind any design discussions or development. I do see crazy shite like "can I run ReactOS on Playstation 2". The forums make your project seem dead, which it clearly isn't.
- You need to fix your flaccid dev community. It needs a larger presence. It needs to be tangible (who is doing what? who are the people? do you have conferences?)
- You need to fix your flaccid dev community. There is a bunch of really useless, out-of-date, confusing and out-right self-inconsistent information on building ROS, and the Git move didn't help (but kudos on the move, it is long overdue). I've tried 4-5 times to do something, but the directions I followed on Win, Ros or Linux all ended up breaking somewhere.
- You need to fix your attitude problems (or your forums). There are people asking reasonable questions, who get actively or passively aggressive answers. Not good.
- You need to fix your toolchain problems. This whole SEH thing is getting out of hand. Does Clang support SEH yet? It might - https://clang.llvm.org/docs/MSVCCompatibility.html. So maybe you need to bail on GCC, or maintain your own fork of it (yes, it's ridiculous that GCC still doesn't have SEH support, and the patents have long expired).
- You need to get a grip on x64 support. Your toolchain problems cannot be a gate (and you can clearly use MSVC for building... so...). IA32 support is great and all, but needs a back seat to x64.
- You need to get a grip on UEFI booting (note UEFI booting does not /necessarily/ mean you need improved ACPI support, in practice)
- Forget Xbox, NewWorld PowerMacs (those were BE anyway) and 32-bit Arm chips (which outside of the Pi are too varied and too few). Targeting 64-bit Arm chips does make sense, though, now that Microsoft has released a client build of Win 10 on laptops and an Arm server vendor demoed Windows Server at OCP'18 (http://www.opencompute.org/assets/Uploads/18150J-Ampere-PPT-...). You will need UEFI and reasonable ACPI support to support ARM64. You can target SBSA and SBBR compliant systems and this will give support for the entire server ecosystem (and qemu VMs, har har).
- You might wish to minkernel-ize ROS as well, so you can boot without a GUI.
- You might wish to update Wiki (and build a list of links to relevant pages) for active subprojects.
I suspect the core devs for ReactOS are very few in number and this probably gives rise to the issues you see. But a rant here won't fix much.
If you don’t want feedback, don’t ask for feedback by posting publicly. My “rant” is a collection of issues I’ve seen for at least the last 7 years of actively paying attention to the project.