14M tests are impressive.
Plus, with this Windows exists no state surveillance involved nor costs with licenses, perfect for VM deployment.
Older software tends to work ok (i ran Borland C++ Builder on it without major issues, beyond the GUI glitches i mentioned), but not perfect. Also old software sometimes tends to include 16bit components that do not work yet with ReactOS.
The file manager was also rewritten at some point and it seems to have issues (e.g. you need to manually refresh the desktop/a folder to see changes, drag-drop doesn't always work, etc). However it is much better than 1-2 releases ago, which shows that it gets a lot of development.
Command-line stuff seem to work perfect (although the current shell is quite primitive) though so, if nothing else it can be used for automated tasks.
IMO they should try to pay a bit more attention to getting the basics of the GUI side working since this will attract more developers who are interested in helping with the higher levels (as higher as working with stuff like user32.dll etc can be anyway) but don't want to mess with the low level stuff (graphics, etc). I think ReactOS is still at a point before the "snowball effect" with its developer popularity.
Possibly some "new" software too? A few months ago on HN there was a thread about the "age" of various software, someone had mentioned that Visual C++ traces its lineage back to 1983's Microsoft C (written in pre-ANSI C and 16-bit x86 assembly for DOS), and I said I imagine they must've thrown that code out when rewriting it in C++ for Win32, but then someone from the VC++ team corrected me: a lot of that code is still in there.
Of course, 64-bit Windows doesn't support 16-bit programs, so I'm not sure if those parts are only still present on builds for 32-bit Windows, or if they're recompiled as 32-bit, or if they're run in a VM or kernel module.
Although considering that 32bit Windows can still run 16bit code, i guess they also need to be able to compile the 16bit-to-32bit bridge code so this is probably another reason why the 16bit stuff exist.
To whom does the Borland C++ builder belong. Because I wonder if there will open a market to get old c++/pascal code running in ReactOS?
There is projects like lazarus and free pascal.
But if you can keep your legacy win32 stuff in a self contained ReacOS vm...
This will solve the enterprise problem of keeping legacy applications contained without win related licencing worries.
Also your long term support looks more promising with ReactOS compared to Win XP; But microsoft will still drag the bone along for a little longer if not indefinitely at a enterprise price, ofcourse.
Me, i bought it off ebay some time ago. Here is a blog post with some details: http://runtimeterror.com/blog/borland-c-builder.html
Note that i remembered wrong: BCB doesn't work out of the box, there is some issue with paths and such (i tried a few hours ago to install it in the latest version). I remember i solved it at the past, but i don't remember how i did it.
> Because I wonder if there will open a market to get old c++/pascal code running in ReactOS?
Well, if ReactOS is supposed to be Windows compatible it should be able to run that software without any explicit support for it since they work fine in Windows 10 (and as you say it is more likely they'll continue working on ReactOS than Windows - after all Wine can run today old 16bit software even on 64bit Linux, unlike Windows).
> But if you can keep your legacy win32 stuff in a self contained ReacOS vm...
Personally i prefer to run things natively because i often use those older tools for "real" work, mainly because of their speed (i write a game engine in C and Borland C++ 5.0 can compile the entire thing in less than a second). C++ Builder can also be very helpful to create a quick and dirty GUI for some C library (merging oldschool retro with bleeding edge, i modified GLEW to work with C++ Builder to create some tests for OpenGL 4.6 that was released a few days ago - being able to easily throw sliders, knobs and other widgets is neat).
*When car manufacturers reach peak saturation with a given model they expand/consolidate their position by improving their product, NOT by making the consumer buying their car the product...!
Well, PCs had been suffering from viruses long before they got network adapters...
One thing I wish would get fixed (though I understand why it hasn't been yet) is the USB boot option. Most of the physical devices I want to run it on lack a CD drive.
Still I'm glad someones working on this project and will keep hoping the USB support gets fixed in the future
Edit: Ok I'm impressed, apparently it can even run Doom III https://www.youtube.com/watch?v=rluGgjcXtEY
Can run? That was unplayable choppy. Guess it could be the machine though.
I would be really interested in this use case.
Congrats for all this work through years!
(I was one of the two original authors of msitools, taking care of porting Wine's msi DLLs to a POSIX environment. The other guy took care of making the API less Windows-like, ported .cab file support and wrote Wixl).
Another option is to use AppVeyor CI + Microsoft's Vcpkg , it's also integrated with CMake and require no manual setup.
I know both projects share a lot of code, so if one is better, why is that the case?
Device drivers: Driver.cab is 60MB.
Localizations: LANG folder takes 100MB.
.NET Framework: 41MB.
Various migration tools to upgrade from Win95: 32MB.
Plus, everything in the base system is in two copies, one for the boot environment and one for the installed version, similar to initramfs and RPMs for Linux.
They probably never tried to reduce the size.
Also previously discussed here:
It turns out that the overall Windows bloat due to XMP tags amounts to something like 5MB.
There are mainly two. Firstly ReactOS is open source. Secondly ReactOS is Free. Also Windows (especially the newer versions) are known to monitor all your activity by default. So if you're concerned about your privacy or just don't want to share any personal info, we promise (and you can check our source code) that we don't track any of your data.
So yeah, they are (at least were) monitoring not only what sites you went to, but also what you typed into them.
On top of that, I have several old (XP-era) laptops which still boot, still can play my older games and get on the Internet, etc. They're not really capable of running even Win7. ReactOS allows me to run a newer OS on those old IBM battleaxes.
Frankly, I'm only really worried about malware somehow sneaking aboard the thing, which is why it's on-network in the first place. I don't want people plugging flash drives into it. And fortunately, there are still antivirus products that support Windows XP, which keeps the riff-raff out.
Having said that, ReactOS still needs quite a bit of work to cover that niche, in my opinion.
There's lots of legacy software targeting win32 out there.