Sorry for the non-developer intrusion, this is the point of view of an IT
technician that would happily substitute Windows machines with ReactOS machine
in an hypotetical future.
To me, this looks like an extension (and a perilous one) to the “which NT
version should we target?” discussion, whi
Dear Ricardo,
Firstly, Win16 application support doesn't interrupt our project. It
strengthens us. On technical view, supporting them doesn't make any design
change to NT architecture, apps won't be able to access hardware directly. Like
any app, they'll obey the rules.
Secondly, there are a n
Dear Ricardo,
Firstly, Win16 application support doesn't interrupt our project. It
strengthens us. On technical view, supporting them doesn't make any design
change to NT architecture, apps won't be able to access hardware directly. Like
any app, they'll obey the rules.
Secondly, there are a n
17.03.2017, 14:56, "Can Tasan" :Dear Ricardo,
Firstly, Win16 application support doesn't interrupt our project. It strengthens us. On technical view, supporting them doesn't make any design change to NT architecture, apps won't be able to access hardware directly. Like any app, they'll obey the
Dear Can,
Your argument would hold if the objective of the project was to support edge
cases by coding legacy support to eliminate the need for other people to
modernize their infrastructure. Is this what ReactOS wants to achieve as its
main goal?
I would get your argument if ReactOS was even r