Development on this project to create an Open Source clone of Windows 95 started way back in 1996. 2026 means it has now been 30 years in development, but this project still remains in an alpha state.I don't mean to sound impatient or anything, but what's the hold up? Is it gonna take another 30 years before it reaches the beta stage?
>>107863163One of the devs showed up here and called it saying they don't even care about gettiing anything to work except it helps testrun shit for wine.
>>107863163And yet Windows 11 is so bad ReactOS will soon be better despite still being an alpha.
>>107863263that'd be kind of based, a Working Win2k/XP tier OS that's well supported. a lot of nonfree shitware still depends on that and I've seen DOS ware still in active use. Surprised industry cucks don't fund this more. It's pretty important, but I guess they're all money pinching retards.
>>107863163Why don't you work on it too then, or are your skills limited to just whining on 4chan and very likely also reddit?>>107863193stop making shit up idiot
>>107863347I thought there were a few good GSoC for it recently.
>>107863163From what I know they managed to get every amd gpu xp driver working, I think intel too, not sure. The changes are being reviewed for the next version. But don't expect the same level of performance, other parts of the OS are slowing it down, and they didn't bother to work on it because the goal for this year is vista+ compatibility which they have worked on for years in separate repos.The biggest problem is the memory manager which is incomplete and buggy and no one actually knows how to improve it atm.Besides that things are looking good, progress is slow because it turns out certain parts of windows were extremely smartly designed, unlike the trashfire that is linux.
>>107863163>for 30 yearsIt's only really been in active development since the russkies took interest in it desu
>>107863163>windows source is available and likely already ingested by the copyright laundering machines>jeets on hackernews swear up and down that they are 100% more productive because they vibe coded their dream hobbie project in a weekend or whatever>reactos is still shit
>>107863573>From what I know they managed to get every amd gpu xp driver working, I think intel too, not sureSource?
>>107863163>Is it gonna take another 30 years before it reaches the beta stage?Yes. And you have an issue with that, then don't use it.
source code for I think XP is floating around somewhere, but apparently the devs won't even look at it out of fear of getting v& by microslop
>>107863809I lurked their discord
>>107863163If you think that's crazy, read up on GNU Hurd.
>>107863761It's almost like vibe coding is bs....
>>107863163>30 yearsBig deal.Windows has been in development for 40 years
>>107863347Look it up nigger, it was posted like a couple weeks ago.
>>107863163It will never be usable, this is by design. It could have been done ten times over by now if it was actually intended to be usable.
>>107865302stop believing anything anonymous tards on 4chinks lie about>>107865307another low iq 4chinker, this place is a containment zone for idiots and kids
>>107865282>40 yearsholy shit, windows is an unc OS fr lmao>>107863163reactos is a useless piece of shit that doesn't even run on real hardware because the devs are too busy huffing their own farts about "muh clean room engineering". they're all russians who are exempt from american copyright, but they still act autistic about the source code leak because uhhh... MUH GOBBYRIGHT!
>>107864062We dont really need the Hurd, because we have Linux-libreBut if Torvalds didnt write a free kernel, then the struggle to make a free kernel would continueThey couldve adopted maybe one from BSD, but there was already the drama about BSD as a whole containing code from Unix. And GNU wanted to avoid all nonfree code at all costs
>>107864062>If you think that's crazy, read up on GNU Hurd.In both cases, Linux (or GNU/Linux, if you prefer) is what has set back and continues to hold back the development. If Linux had never been created or took off like it did, then HURD AND ReactOS both would have gained a lot more momentum in their development, because there would have been a need for it. Linux made these things less necessary so it took the wind out of their sails, so to speak.Now, with that being said, I'm not even entirely sure what exactly ReactOS accomplishes or would accomplish that isn't equally accomplished by Linux+wine. Does anyone know of anything?I still think ReactOS is going to happen anyway. Most of it shares the same groundwork as WINE anyway, so as WINE advances, ReactOS will be propelled along forward with it. I also think ReactOS development will accelerate once it reaches a certain critical mass when it comes to usability. When it hits a point where people can start using it as a daily driver, then you'll see much more interest in it and thus development. For now its slow because it hasn't yet reached that point.
>>107867396> Most of it shares the same groundwork as WINE anywayWhy do people keep spreading this nonsense. ReactOS shares some user mode libraries with Wine. But all the core components are totally different. Implementing win32 on top of Linux is a very different thing to implementing an actual NT operating system.
>>107863163open source wankers do be like that
>>107865282>40 years>Task Manager still freezes for several seconds
>>107863830If they look at the XP source code but rewrite it in their own style then they have perfect plausible deniability.
>>107863163Nobody cares about old Windows compatibility anymore. Almost all of the shit tier devices the OS was made for are out of commission (it was supposed to be a FOSS replacement for Win2k/WinXP business machines).We use compatibility layers, containers and virtual machines nowadays. If you need a Windows 2k/XP program to work you'd just run it in a VM or inside WINE.
ReactOS is based on knowledge of copyrighted code. It is a potential legal nightmare without any upside.
>>107867962The source code was not even needed. For the most part the windows code is not very complex, the disassembly with debugging symbols is almost as good as source. ReactOS could have been finished a dozen times over already even without the source, if it were actually intended to be finished. But its not, the project has been setup for failure due to some fundamental decisions.
>>107868969>>107867962The XP/2000 code could just be documented and a third party without knowledge of the code could write it.Writing in their own style would not fly in the courts because if MS sues they should be able to answer and prove that they never saw the original code.The same for disassembly, the same team that disassembles can't be the same team that writes the code, they should just provide specifications to the "clean" team. Disassembling and translating something based on it is the same as reading the code, that is copyrighted.
>>107864062>Wildebeest often graze in mixed herds with zebras, which gives heightened awareness of potential predators. They are also alert to the warning signals emitted by other animals such as baboons. >Aerial photography has revealed that a level of organisation occurs in the movement of the herd that cannot be apparent to each individual animal; for example, the migratory herd exhibits a wavy front, and this suggests that some degree of local decision-making is taking place.>While having the appearance of a frenzy, recent research has shown a herd of wildebeest possesses what is known as a "swarm intelligence", whereby the animals systematically explore and overcome the obstacle as one.Ok now what? How does this relate to operating systems?
>>107863163tr00nix users ruined it
>>107869046That aside, I will explain why ReactOS will never be finished and has been set up for failure.1. gcc. msvc is the only compiler appropriate to develop NT. The fact that they support gcc kneecaps the entire project.2. Breadth first approach, developer effort is spread too thin, unfocused. They should have developed the core components to 100% instead of messing around with unimportant nonsense. Like why does ReactOS have a clone of mspaint, what a profound waste of developer effort.
>>107869128>what a profound waste of developer effort.The people working on it wouldn't have worked on core components anyway. So your only options is 1) have the mspaint clone, 2) don't have the mspaint clone
>>107869046>f MS sues they should be able to answer and prove that they never saw the original code.Where does law work backwards like that, in 'murrica? Pretty sure that in a court of law in a civilized country one has to prove that someone did something, not the other way around.
>>107863830>can't look at code of product you're reimplementing no shit. Wine has the same rule. reading even a single line legally taints you forever.
>>107869189They give "proof", like usage of similar variables etc, and how do you would respond? That you have the same idea?If the judge is convinced then you have the prove them wrong.
>>107869365>That you have the same idea?Yes, that's how it works. There's only so many ways you can code behaviors.
>>107869359how do they know how that code looks like if they didn't see it?how about docs for windows APIshow about Petzold style code?how can they tell apart that code from other code, especially if they never seen that other code?
