Urgent Design Questions
Moderator: Moderator Team
Urgent Design Questions
Hello,
I'm researching ReactOS and had a few questions about the design of ReactOS, I looked everywhere to find answers to these questions but was unfortunately unsuccessful, so hopefully you guys will have the answers to my questions. Anways here is the list of questions:
-1- What are the major design goals and the main areas of application?
-2- What are the process and memory models used?
-3- What kind of: Scheduling, file system management, security, networking, etc. does ReactOS adopt/provide?
-4- What programming environment is used, including programming languages and tools?
Thanks.
I'm researching ReactOS and had a few questions about the design of ReactOS, I looked everywhere to find answers to these questions but was unfortunately unsuccessful, so hopefully you guys will have the answers to my questions. Anways here is the list of questions:
-1- What are the major design goals and the main areas of application?
-2- What are the process and memory models used?
-3- What kind of: Scheduling, file system management, security, networking, etc. does ReactOS adopt/provide?
-4- What programming environment is used, including programming languages and tools?
Thanks.
1. Our main design goal right now is an open-source operating system, based on NT architecture and binary compatible with NT 5.2 (Windows 2003). Areas of application are the same as with current Windows XP/2003. ROS is to be freely available XP/2003 replacement OS, capable of running Win32 applications and NT model device drivers.
Passing 2 and 3 to someone more knowledgleable.
4. ROS is written mostly in C, with some components in ASM and few pieces of C++. We support building with Ms Visual Studio, but our main building tool is RosBE - GCC/MingW32 based Building Environment, capable of building ROS OOTB on both Windows and *nix systems. As for programming environment, we do not have our own IDE. Some use VS, others KDevelop or even notepad-like apps with syntax highlighting.
Passing 2 and 3 to someone more knowledgleable.
4. ROS is written mostly in C, with some components in ASM and few pieces of C++. We support building with Ms Visual Studio, but our main building tool is RosBE - GCC/MingW32 based Building Environment, capable of building ROS OOTB on both Windows and *nix systems. As for programming environment, we do not have our own IDE. Some use VS, others KDevelop or even notepad-like apps with syntax highlighting.
-
- Posts: 318
- Joined: Wed Jun 15, 2005 8:19 am
-
- Posts: 318
- Joined: Wed Jun 15, 2005 8:19 am
I thought of it not really as improving the core design, but more improving the way it is implemented, after all it is a vision 'ported' to sourcecode, and I could imagine there's different ways of doing just that...Ged wrote:It's difficult, if not impossible to improve on the design of some of the smartest programmers on the planet.
I think people underestimate the skill of the MS core devs, and the brilliance of the NT design.
-graey-
-
- Posts: 318
- Joined: Wed Jun 15, 2005 8:19 am
While the core devs of Windows may be geniuses, the overall effect after being passed down through the corporate tubes is a product of pure bullshit. The only thing bringing me back to even trying Windows Vista after its complete and total failure is my hopes that the bullshit can be stripped from its vastly improved core. It's almost as if the geniuses hand down the golden code after it's finished, then MS greedily snatches it up and hands it to the "user experience" monkeys and say "HERE YOU GO GUYS, FUCK IT UP!". All that talent wasted... on Aero.
Which is exactly why I hope the ROS guys can actually continue this project. Maybe you'll soon get help from an ex-Microsoft (or maybe even disguised current MS core coder - not that you'd ever find out) coder that's fed up with the way MS fucks up and bastardizes everything of theirs... then we'd see some real progress.
Then on the flip side, maybe some MS lawyer will find some snazzy little patent they would love to shove up ROS's ass and we'll all be screwed. That's the one major thing I'm concerned about at this point. If it does plan on being binary compatible with MS Windows, wouldn't that make it totally illegal?
Which is exactly why I hope the ROS guys can actually continue this project. Maybe you'll soon get help from an ex-Microsoft (or maybe even disguised current MS core coder - not that you'd ever find out) coder that's fed up with the way MS fucks up and bastardizes everything of theirs... then we'd see some real progress.

Then on the flip side, maybe some MS lawyer will find some snazzy little patent they would love to shove up ROS's ass and we'll all be screwed. That's the one major thing I'm concerned about at this point. If it does plan on being binary compatible with MS Windows, wouldn't that make it totally illegal?

Who is online
Users browsing this forum: Ahrefs [Bot] and 2 guests