4 ms·

Hello from ReactOS team! We don't use the leaked code from MS, We don't use Windows Research Kernel, We thank you for the PR campaign you have stared 'pro b

Hello from ReactOS team! We don't use the leaked code from MS, We don't use Windows Research Kernel, We thank you for the PR campaign you have stared 'pro bono' for our project! ;D

notus 7y ago
You didn't spell started correctly both on here and on quora aka thanks for the low effort canned response. Maybe try addressing their points directly. This is bad PR for you.
- michaelmrose 7y ago
  You mean the accusations for which the accuser refuses to provide any proof?
- codedokode 7y ago
  What "points"? Axel didn't provide a single example of what could be allegedly copied code.
amrrs 7y ago
Why would you call it a PR campaign if it wasn't favoring you? Just curious.
- johnmarcus 7y ago
  because a lot of people probably just learned about ReactOS as a result of this controversy. "There's no such thing as bad press." -someone
  - lacampbell 7y ago
    The controversy is just unverifiable claims from a Microsoft employee. ReactOS comes out looking pretty good.
- jeditobe 7y ago
  Even very dirty river water would still spin your mill, as long as the mill itself is good. This guy literally confirms that one little open source OS could be as good as Windows $)
- yjftsjthsd-h 7y ago
  Probably because it makes far more people aware that ReactOS even exists.
- redder2 7y ago
  You never heard of "all publicity is good publicity"?
- testvox 7y ago
  Not only is ReactOS getting a lot of coverage it otherwise would not have, but the core claim seems to be that ReactOS is actually such a good re-implementation of Windows that actual Windows engineers think it couldn't have been accomplished without using the Windows source code.
pizza234 7y ago
OP wrote "If any of the presumed authors wants to chime in and explain the similitudes, I’m happy to change my mind". Since you're from the team, could you provide some example explanations? Technical arguments are surely significant, rather than a purely rhetoric answer.
- shmerl 7y ago
  I don't think they need to. The OP blames ReactOS, the burden of proof is on him, if he thinks it's an issue. Otherwise it's called trolling.
- codedokode 7y ago
  Axel didn't provide any examples of allegedly copied code, so what can they explain?
Udo 7y ago
This is an utterly insufficient answer to the allegation that you copied internal data structures entirely from the NT kernel, including (why?) their names. Brushing this off as a free "PR campaign" only works if those NT programmers simply made everything up. That's possible, because we as the general public have no way of knowing. But it's hard to ignore that there are just two possible scenarios here, nothing in between. Could you please clarify: If MS people say they do recognize verbatim code from NT in your source, are they lying? If they're not lying, what happened?
- dragonwriter 7y ago
  > This is an utterly insufficient answer to the allegation that you copied internal data structures entirely from the NT kernel It's quite sufficient when you consider that, unless the allegation is made in a court of law, it's in ReactOS’s interest for it to be perceived as plausible. Being perceived as either an actual (if unauthorized) fork of Windows or as something that a Microsoft insider could reasonably mistake for one is not bad for ReactOS. And if Microsoft is going to bring the allegation in court, no matter the merits, the lawyers defending ReactOS aren't going to want lots of detailed public statements to have been made first. > Brushing this off as a free "PR campaign" only works if those NT programmers simply made everything up It works and, I'd argue, is the only sane strategy so long as Microsoft isn't suing them. Because, among other reasons, without such a suit it is nothing more than a free PR campaign especially if it is true. Admittedly, it doesn't maximize imaginary internet debate points, but while that maybe be OPs interest, it doesn't seem to be ReactOS’s. (Also, probably not Microsoft’s, who I imagine so long as they aren't suing ReactOS would prefer not drawing attention to it, either.)
  - Udo 7y ago
    I don't disagree with your assessment from a PR point of view, I guess I was just hoping the open source community would hold itself and others to higher standards. Being technically not provably guilty in a court of law is not exactly the peak of virtuousness.
- jeditobe 7y ago
  Well, now please re-read your statement Do you understand that internal data structures entirely from the NT kernel, including (why?) their names != verbatim code from NT in your source The program code is logic first of all. For the similarities of names and structures itself - the answer is in this already mentioned video https://www.youtube.com/watch?v=2D9ExVc0G10&t=9m53s https://www.youtube.com/watch?v=2D9ExVc0G10&t=9m53s from the 9:53 moment of time. TL:DW there are a lot of legal ways of obtaining names of variables, exported functions and structures
cptaj 7y ago
Heh, thats a very guilty looking answer. True about the free campaign but that might backfire.

Hello from ReactOS team! We don't use the leaked code from MS, We don't use Windows Research Kernel, We thank you for the PR campaign you have stared 'pro bono' for our project! ;D

notus 7y ago

You didn't spell started correctly both on here and on quora aka thanks for the low effort canned response. Maybe try addressing their points directly. This is bad PR for you.

michaelmrose 7y ago
You mean the accusations for which the accuser refuses to provide any proof?
codedokode 7y ago
What "points"? Axel didn't provide a single example of what could be allegedly copied code.

amrrs 7y ago

Why would you call it a PR campaign if it wasn't favoring you? Just curious.

johnmarcus 7y ago
because a lot of people probably just learned about ReactOS as a result of this controversy. "There's no such thing as bad press." -someone
- lacampbell 7y ago
  The controversy is just unverifiable claims from a Microsoft employee. ReactOS comes out looking pretty good.
jeditobe 7y ago
Even very dirty river water would still spin your mill, as long as the mill itself is good. This guy literally confirms that one little open source OS could be as good as Windows $)
yjftsjthsd-h 7y ago
Probably because it makes far more people aware that ReactOS even exists.
redder2 7y ago
You never heard of "all publicity is good publicity"?
testvox 7y ago
Not only is ReactOS getting a lot of coverage it otherwise would not have, but the core claim seems to be that ReactOS is actually such a good re-implementation of Windows that actual Windows engineers think it couldn't have been accomplished without using the Windows source code.

pizza234 7y ago

OP wrote "If any of the presumed authors wants to chime in and explain the similitudes, I’m happy to change my mind". Since you're from the team, could you provide some example explanations? Technical arguments are surely significant, rather than a purely rhetoric answer.

shmerl 7y ago
I don't think they need to. The OP blames ReactOS, the burden of proof is on him, if he thinks it's an issue. Otherwise it's called trolling.
codedokode 7y ago
Axel didn't provide any examples of allegedly copied code, so what can they explain?

Udo 7y ago

This is an utterly insufficient answer to the allegation that you copied internal data structures entirely from the NT kernel, including (why?) their names. Brushing this off as a free "PR campaign" only works if those NT programmers simply made everything up. That's possible, because we as the general public have no way of knowing. But it's hard to ignore that there are just two possible scenarios here, nothing in between. Could you please clarify: If MS people say they do recognize verbatim code from NT in your source, are they lying? If they're not lying, what happened?

dragonwriter 7y ago
> This is an utterly insufficient answer to the allegation that you copied internal data structures entirely from the NT kernel It's quite sufficient when you consider that, unless the allegation is made in a court of law, it's in ReactOS’s interest for it to be perceived as plausible. Being perceived as either an actual (if unauthorized) fork of Windows or as something that a Microsoft insider could reasonably mistake for one is not bad for ReactOS. And if Microsoft is going to bring the allegation in court, no matter the merits, the lawyers defending ReactOS aren't going to want lots of detailed public statements to have been made first. > Brushing this off as a free "PR campaign" only works if those NT programmers simply made everything up It works and, I'd argue, is the only sane strategy so long as Microsoft isn't suing them. Because, among other reasons, without such a suit it is nothing more than a free PR campaign especially if it is true. Admittedly, it doesn't maximize imaginary internet debate points, but while that maybe be OPs interest, it doesn't seem to be ReactOS’s. (Also, probably not Microsoft’s, who I imagine so long as they aren't suing ReactOS would prefer not drawing attention to it, either.)
- Udo 7y ago
  I don't disagree with your assessment from a PR point of view, I guess I was just hoping the open source community would hold itself and others to higher standards. Being technically not provably guilty in a court of law is not exactly the peak of virtuousness.
jeditobe 7y ago
Well, now please re-read your statement Do you understand that internal data structures entirely from the NT kernel, including (why?) their names != verbatim code from NT in your source The program code is logic first of all. For the similarities of names and structures itself - the answer is in this already mentioned video https://www.youtube.com/watch?v=2D9ExVc0G10&t=9m53s https://www.youtube.com/watch?v=2D9ExVc0G10&t=9m53s from the 9:53 moment of time. TL:DW there are a lot of legal ways of obtaining names of variables, exported functions and structures

cptaj 7y ago

Heh, thats a very guilty looking answer. True about the free campaign but that might backfire.