![]() Inbuilt sandboxing would be another great thing to have in ReactOS, from both a security and stability standpoint. Heck, maybe a clever hacker could port WINE (aww, I made a lame pun □) and use it for running particularly troublesome apps. ![]() Now, I know the idea is to make it a Windows clone, and as such it will never be entirely *nix-ey, but a working *nix subsystem would kick ass and make it easier to port other open source programs to the OS. ![]() I think it would also be cool if they made it POSIX compliant as well, with support for things like the X Windows system. It would be cool if they could set it up so that things that merely use Win32 API functions can be handled natively, while the x86 emulation is used only for things that absolutely require it. It makes me wonder if maybe a full x86 emulator is in the works for things like the ARM version of the OS. I like the fact that it doesn't rely on V86 mode, and as such can be ported to platforms other than 32-bit x86. The one thing that REALLY impresses me about ReactOS however, is its NTVDM implementation. I honestly can't wait for the day where ReactOS can replace Windows for most users altogether, especially since M$ have been driving Windows into the ground with all the telemetry and forced updates and other stupid bullshit. It just goes to show how hard the ReactOS team have been working to make this a viable OS. In all seriousness though, that's quite a significant list of features. Though for the current desktop systems this is not a problem. Here is a recent article about their NTVDM, though it does not say about using DosBox code.Īlso not a word about the downside of full software emulation: slower. I should go and look at the sourcecode for that component to see what they've done. If memory serves, they modified DOSBox to serve as their OS's NTVDM replacement not too long ago.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |