That's the whole point. NOT all core components are THEIRS to "open source", and they cannot cleanly separate them without having to re-develop parts. I just gave an example, but the issue is general. It has to do with the problem that licenses can be given for specific usage manners... but not for ...

Well, AFAIR, they indeed considered doing this. Windows per se makes rather little money, and "binding the customer" for their other products appeared even more advantageous. - The problem, and why their legal department killed the idea: Windows contains a lot of third-party-code which has been lice...

Your real issue is that "Windows is not Windows". It is a permanently moving target. You have two options: - create a sort of "legacy OS" like FreeDOS (and optionally: develop from there to new heights, the way C64 still gets improvements...); or - "run after the main target", but here, you clearly ...

I say, "drop it". It is 2018. Unless this shall become "Retro OS" (then by all means, go for it!)...

And EXACTLY WHAT will you do with an ARM port? - ReactOS is only an OS, not a "suite of apps"! So will you then handle compiling everything on ARM by yourself, from Firefox to LibreOffice? It "sounds nice", but is entirely pointless in a greater perspective right now.

Ah, and dizt3mp3r: Your message to them on their Github-page was ... brilliant. I mean, I really could learn something from you there - in particular the rhetoric twist in the beginning, "It is an answer to the concern but it does not resolve it", was amazing - you stood your ground firmly, yet very...

Oh, I am sure we all have our thoughts regarding this issue. But they are not important now: the matter has been reviewed and handled. If that is the outcome - that is the outcome. If anyone is dissatisfied with this, he may draw his own conclusions and decisions from here on. And yes, in our projec...

The problems are going in several directions: 1. if you do not defend a brand, you may forfeit your right to defend it later on; 2. the longer you wait, the easier you get a time bar problem; 3. thank you for telling me that Aleksey is fireball. I PM-ed him, too; 4. German attorneys have sometimes a...

Absolutely. Do contact Aleksey. I just didn't know his username to PM him together with others about this. In the past, he has shown great effort to defend the interest of the project and to spread its fame, so I am sure he will co-ordinate action suitably, whether it means to initiate legal steps, ...

Let me make this plain: Their reply on the GitHub page is RIDICULOUS, and NATURALLY they would reply that way. Like, what the hell do you think will they say? "Hey, you caught us, we totally infringed your logo and brand"? They act defensive. And while I am by no means trying to give you "legal advi...

Look at this: https://facebook.github.io/react/ Now this "React", with a logo very similar to yours, is practically served on the silver plate. And it belongs to Facebook. You might consider squeezing them for money. This is plainly shameless. Seriously, talk to your lawyers, cases have been won wit...

Delete this nonsense already or at least banish it into offtopic country... otherwise I will have to ask here what sort of hotdog flavour to choose...

I think if OP proves anything, it is that ReactOS devs are like a few hundred times more efficient than MS devs. This battle will not be won by having PERFECT compatibility: it will be won by having SUFFICIENT compatibility. That matter is far from settled either way, but so far, ReactOS is doing GR...

As jimtabor mentioned, the underlying issue is not actually Office. The underlying issue is that ReactOS shall not turn into FreeDOS. That is, an "antique / memorial OS for dead software".

Haiku did not manage a realease for an eternity. "But take the nightlies"... yeah, go take the nightlies yourself. The point is: releases are POINTS OF REFERENCE. When you say, "I got version A.X. and it got a bug", then people will try to sort it out WITHIN A.X. If the only answer you get is, "yeah...