>>24750
NTA but my experience was the opposite of your image.

>>24747
ReactOS is a decade away from stable only in the same way the fusion power is always a decade away. In reality its closer to never.

>>24750
Linux 1.0 1994
Linux 2.0 1996
IBM partners with Red Hat 1999
IBM invests $1 billion 2000

By the time they started investing, they were already using it as a drop in replacement for Unix.

Can't wait for Tf2 to run on ReactOS

>>24651
can someone explain to me why the ReactOS win32 implementation is somehow more desirable than the wine win32 implementation?

>>24755
Because you sidestep linux and its retardation

>>24669
found the pig

>>24747
>>24750
loonix didn't even have 1/5 of the things that reactos has implemented at release and for much of it's life

>>24711
The source code to windows 95b all the way up to I think 7 was released, including the server editions.
The russkies probably have a striped to the bone enhanced version of windows 7 that can run on a i386 by now.

>>24755
The Linux kernel is stable, as a headless server. The desktop part is an unstable clusterfuck. Hence the invention of immutable distros and flatpak (and similar). We need a real desktop OS.

>>24760
>The Linux kernel is stable, as a headless server. The desktop part is an unstable clusterfuck
That will never happen because Linux has no stable ABI thanks to Linus' autism, unlike Microsoft devs who designed everything "as if" from the start.
That's the reason for that phrase of "Win32 is the only stable ABI on Linux" which basically started as a meme but it is slowly becoming a reality thanks to the efforts of WINE and Valve devs who are literally compiling stuff under WINE/WINE-like software instead of making proper Linux/UNIX/GNU software like before this decade.

>>24709
>Or just Microsoft's own hubris?
Microsoft exclusive feature, you can use it on with C

>>24755
they're the same thing, reactos and wine share a lot of code for obvious reasons

>>24761
>That will never happen because Linux has no stable ABI thanks to Linus' autism, unlike Microsoft devs who designed everything "as if" from the start.
The Linux userspace ABI issues aren't because of Linus and the kernel, but because of the glibc and all the other userspace libraries not having a stable ABI to save its life. Ironically the GNU part of GNU/Linux is doing all the damage. And I hope you're not conflating userspace ABI with the kernel driver ABI, which yes it could be more stable but Linux wasn't really designed to have 3rd parties make drivers and NOT merge then in the kernel and nobody(not even nvidia) seem to care that much.

>>24764
>Linux wasn't really designed to have 3rd parties make drivers and NOT merge then in the kernel
Which is dumb, because Linus and the rest of the devs expecting everyone to open source their drivers, especially big name companies, was just too naive.
At least Microsoft devs knew damn well we don't live in an ideal world and just set the guidelines about what a Windows drive should be and let everyone do their business.
And yeah, bad third-party drivers actually used to fuck up your system if they were bad enough, but those things got more or less sorted out by the times of Vista.

>>24761
People are constantly touting Windows as having stable ABI and shit, but quite a lot of old software, especially games, have stopped working on newer versions of Windows. That doesn't sound very stable to me.

>>24651
sorry im stupid what's that aint that just linux?

>>24767
It's an OS with his own kernel that aim to be fully compatible with Windows

>>24768
well that is actually great

that would be a great alternative to windows

>>24769
Yeah but it won't be ready anytime soon sadly.

Why can't we re write windows 7 in rust and add support for windows 10 applications?
And while we're at it fully integrate the linux kernel so it can run anything?

Is there any reason that windows 7 couldn't run windows 10 shit, I mean it's still x86 code right?

Can someone please link me the windows 7 source code because I'll do this myself if I have to. I have unlimited time, no job and unlimited ritalin

>>24771
Win7 source didn't leak, XP did

>>24772
That's just useless. I thought I saw the windows 7 code get leaked like a year or two ago

>>24699
That's why there's something of a case to be made for go the other way:
>start with virgin windows server 2003
>write a basic hal
>test, bugfix, test, bugfix, test, test, test until that hal works perfectly on windows
>reimplement basic drivers required to start the machine such as i8042, classpnp, afd, fltmgr, ntfs, etc.
>test, bugfix, test, bugfix, test, test, test until those drivers work perfectly on windows
>reimplement slightly higher stuff such as ntdll, smss, etc.
>test, bugfix, test, bugfix, test, test, test until these work perfectly on windows
Once you know all the above pieces work correctly, it's really not that much work to fix their ntoskrnl implementation. 99% of it is there, it's just - as you point out - wrong in places, and this fucks up everything above it.

>>24706
>An open source version of windows without all the damage done in Vista and newer would be very useful.
the leaked source code of NT 5 is sitting on archive.org lmao

>>24682
That's pretty cool, I wonder if anything good runs on it

>>24776
>Krita 3.2.1
>Doom
>Open office
>Dactyloidae browser so you can watch youtube on ReactOS apparently
>Hwmonitor 1.30

>>24775
The source code leak was a pre-release heavy development version. Its not in a good stable state. This made it difficult to further develop as the code is in such a mess, and without it being legal collaboration to unfuck it is very difficult.

>>24766
Try getting an old Linux binary running. It's not going to happen. Microsoft screwing up 0.001% of software compatibility, usually because it was doing DOS things instead of Windows things, is still by far the best out of the 3 choices.

>>24779
I ran a linux binary from 2002 fine. is that old enough?

>>24780
I ran a Windows one from 1993.
If I ran 10 LTSC, I'd be able to run one from 1987.

>>24781
wine runs windows exes too, even 16-bit ones on a 64-bit system. your point?
there aren't any interesting linux binaries that old and without source code available.

>>24782
Oh OK, we're talking about shitty emulators with a 40% crash-to-desktop rate now.
Then WSL runs Troonix programs - and with a way lower failure rate than Wine.

>>24783
on my machine, wine runs everything I need, and I had a lot of baggage coming after decades of windows use. you might want to look at the terminal for errors and install missing dependencies.

>>24784
Good for you.
I need working drivers, however.

>>24651
I genuinely wish ReactOS was more popular.
Maybe not at the level of completely replacing Windows, but at the point of serious hackers taking a liking to it and start to experimenting with the code.
I mean, for example, Haiku has like 2-3 ports of different architectures, and that OS is also niche as fuck, why not ReactOS too?

>>24653
>Usecase ?
Running doom on a toaster.

>>24786
haiku is very interesting and has its own things going on, unlike reactos which is just crawling behind windows (and wine).
if windows was a blossoming platform, not a dying one, there would be a more hacker interest in reactos replicating its insides.

>>24779
>try getting an old linux binary running
You don't need to do this because Linux is open source, so you can just compile the binary for modern hardware. Windows and its programs are all closed source so you can't do this and thus windows needs legacy support to run old programs. There's no use case for the feature to begin with in a world where you can re-compile

>>24789
Lol, try closed source shit like Real Player. Nearly fucking impossible unless you also use an rpm distro from that era, the repositories are still working so you can download dependencies, etc. Not fucking worth it.

>>24788
Everything runs as root on Haiku, so it's never going to be more than a hobby/nostalgia project for old programmers. Sure, they say they'll add real security later, but we all know that it will be too difficult to add that later and it'll never get done. Basically connecting to the Internet with Windows 98 and praying you don't get hacked immediately.

ReactOS's problem is people don't want to put in the time investment for learning Win32 and the NT kernel. Literally the only reason to do it would be hoping to get hired on by Microsoft later.

>>24658
No x64 is only reason Microsoft not suing project

>>24792
They can't sue them because there is no proprietary Microsoft code in the project, the whole point of ReactOS is to be a legal open source Windows.

>>24792
ReactOS is no threat to Microsoft. Its too badly mismanaged to ever become a threat.

>>24794
it's like two guys working on it what do you mean

>>24689
>microsoft audited them 20 years ago
wow

>>24725
You're right. At least publicly, opengl support only became available with the togl library.
I think there might have been some gl tools during its development. I remember the og release of hl2 having config files that mentioned opengl, though I don't remember it being usable AFAIK.

>>24789
>library libshitbox-0.27pl4 conflicts with libshitbox-9.6.5
>library libvanishedin2002-0.65-ALPHA not found
>library libshitbox-0.27pl4 conflicts with libshitbox-9.6.5
>library libremotelyexploitable must be downgraded to version 0.0.1, continue (Y/N)?

>>24697
>>24651
A few years ago I tried running this pile of shit on a PC I built specifically for running old Windows versions. Some stuff worked, but connecting to the internet without ethernet was fucked so I couldn't do much. This computer is using a TP-Link card that has Windows XP drivers so in theory installing the drivers should just werk, but here it didn't. If I'm still alive once 2030 rolls around, I might try again, maybe they'll figure out the wifi situation by then. For now, I think people looking at ReactOS should just try daily driving Q4OS instead since you'll have all the benefits of Linux as well as it's designed to copy Windows's look and feel (especially if you install XPQ4).

>>24699
You're correct, but this project has far bigger issues such as there being only one person in the entire project with the authority to cut new releases, which they refused to do until a retroomer youtuber tested the stable version which was years behind the dev build and complained about how nothing worked. I think since then they might have fixed this issue, or perhaps finally cut a new release due to the aftermath of that video only for the problem to then happen again.

>>24710
It wouldn't take ReactOS devs but some third party taking what ReactOS has so far and patching it with leaked Windows code. And the answer is fucking nothing would happen. Your average normalfag doesn't even have a desktop anymore, most power users are on Linux, and most PC gamers won't give a shit because their GPUs' drivers won't work on ReactOS.

>>24707
Running old shit without the guilt of pirating Windows XP to do it.

17 developers btw
https://reactos.org/wiki/People_of_ReactOS