r/reactos • u/piovono_pancake • 2d ago
A reactOS fork?
https://youtube.com/watch?v=T1WnEJrW9d0&si=Y747hPyImpnGpKN013
u/jmhalder 2d ago
It's been posted here before. It's a lot of AI slop, which people have mixed feelings on. If it's going to progress comically fast, and if competent people can debug it. It is a fork of ReactOS and if they want to slop up their fork, let them. I'm not above playing around with it.
There's a whole conversation about copyrighting or licensing slopped code, but lets not have that discussion today.
6
u/YoYoMamaIsSoFAT32 2d ago
The guy who made it is know in the ROS community and knows what he's doing even if it's AI assisted, so yeah it's not like AI is writing all the code without anyone experienced checking stuff
4
u/ManRevvv 1d ago
the commits are made literally every 1.5 hours by one contributor, clearly the author don't know what he doing
6
u/Artistic_Crazy_7120 1d ago
Assisted by Ai is not the same as AI slop. It will open new possibilities to make ReactOS usable for instance.
2
u/ManRevvv 1d ago
I'll just copy the comment I wrote under one video about libernt and paste it here
the project is honestly quite trash, and it haves so much problems
the dev is one person with dozen of ai agents
the project is obviously vibecoded and "clean-roomed" (but its not, the ai probably was trained on leaked code)
the project is not maintains BIOS boot but for some reason uses NTLDR as default loader (???)
for some reason its way less stable than ReactOS and boots from hard drive in 1 out of 10 cases
the project maintains 103298102 architectures but can't run any properly (reactos still have issues with WoW64 even after 12 years lol)
reactos suck even at nt6 compat (and nt5.2 is like half-implemented still), i won't even mention nt10, so clearly even for one person with ai agents its years and years of work and after like 2 years or something no one will maintain it
It’s the same as building a large three-story villa on a dilapidated foundation that was laid back when Theodore Roosevelt was president
3
u/Different_Water7545 2d ago
why fork? send patches and get reactos there
10
5
u/KasanesTetos 2d ago
The ReactOS team is still deathly afraid of potentially infringing on copyright. AI code is still in somewhat of a grey area, so the ReactOS team haven't been embracing it like most other projects. While I can understand the concern, the truth is, they're probably just gonna be left behind and forgotten about by forks (like this one) who aren't afraid of copyright concerns and are going full steam ahead with AI code.
4
u/TheJonThomas 1d ago
They won’t touch ai because there’s a chance the it was trained on Microsoft copyrighted code at some point, and if it was there’s a chance it could spit out that copyrighted code at any time. That chance isn’t worth getting their life destroyed by Microsoft lawyers.
4
u/RAMChYLD 1d ago edited 1d ago
Plus this has already happened once. As I’ve mentioned before some ex ReactOS developer who landed a job at Microslop suddenly accused ReactOS of using Windows source code taken from materials that was released to universities for teaching purposes. Suddenly droves of lawyers and auditors came out of nowhere and demanded to audit their code. If I’m not mistaken they were also dragged to court several times over how some parts of the code “looked suspiciously similar” though it was proven then and there that the code cannot be implemented other ways. They have to stop development and freeze contributions for a year for the audit. Even after the audit the code had to remain frozen for another two or three years, and it took them 5 more years after that to recover their activity level.
0
u/Silent-Web-6499 1d ago
Nothing about this is accurate. Starting with the fact the guy that left for Microsoft and the guy that accused them of stealing code are 2 different guys.
2
u/RAMChYLD 1d ago edited 1d ago
Even if my memory is failing me, it stalled the project for a decade (I have been actively watching ReactOS for years now, and even donated to their Indiegogo when they needed funds for development, no doubt after those bloodsucking lawyers and auditors had drained them considerably). If this were to happen again it would be devastating. The auditors thing was accurate as I remember it and unless I misunderstood, according to Wikipedia they did have to go to court at least once to answer for why certain code looks like it was lifted out of samples Microslop provided to universities.
2
2
u/TomDuhamel 1d ago
That's a surprising assumption, at best. I really don't see how you'd think MS would have let anyone train an LLM on their private code.
5
u/TheJonThomas 1d ago
Sure, the people who are getting sued for scraping the entire internet would totally not train LLM's on copyright code that gets uploaded to github.
1
u/DegenerateCuber 1d ago
There's a bunch of leaked source code for different Windows versions, I think it's pretty safe to say all the major models have been trained on it, considering how little they seem to care about what they take.
5
u/Different_Water7545 2d ago
Oh I didn't realize it was AI, I should've guessed that. In that case I get it. Myself I think it should stay out of ReactOS, but to each their own
1
u/User_Typical 1d ago
I wish I could get it to work in VirtualBox. After much experimentation, I finally got to the "choose language" screen with the ISO, but as soon as I tried to use the mouse pointer, I got the BSOD.
1
u/ManRevvv 1d ago
didn't booted at all in virtualbox, just random glitches and BSOD without text. in VMware I had same thing
1
u/MentalLavishness6644 13h ago
os that will never be finished adds new fork that will never be started
1
u/ShatteredRubies 9h ago
Why on earth would they call it that..? "LiberNT" Is that supposed to be a play on the word liberate? If not then I got no clue. Its just a bad name otherwise. (In my own personal opinion of course)
1
u/TheRealCarrotty 1d ago
hm, should i use ReactOS with old app support or an AI vibecoded slop fork of ReactOS for modern apps.
1

8
u/User_Typical 2d ago
did you try installing any recent 3rd party software?