FSF - priority-projects
Posted: Fri Aug 22, 2014 5:12 pm
I have come across this FSF website and ReactOS is not listed there. Would it be of benifit to the ReactOS project if it were!
I don't think they care about the architecture used, it's far more along the lines of what Z98 said. They are against proprietary software, and ReactOS is neutral about it, and one of the biggest reasons to use it is if you depend on some closed software that isn't ported (otherwise, you could theoretically port it yourself), so they probably see it as promoting the use of proprietary software. That says nothing about them liking or not the architecture, and AFAIK their moral doesn't claim any value of good or evil to such thing.EmuandCo wrote:FSF hates us for not fighting to kill windows and it's architecture. Will not happen.
A bit off-topic, but one reason I dislike the FSF: They don't realise that not everybody wants to take a look at, or cares about, the source code.mrugiero wrote:I don't think they care about the architecture used, it's far more along the lines of what Z98 said. They are against proprietary software, and ReactOS is neutral about it, and one of the biggest reasons to use it is if you depend on some closed software that isn't ported (otherwise, you could theoretically port it yourself), so they probably see it as promoting the use of proprietary software.
They do realize that, they specifically say people who can't program can still feel assured that those who can are able to review and modify the source, whereas with proprietary programs you're stuck with what you've got, spyware and all.The_French_Rat wrote: A bit off-topic, but one reason I dislike the FSF: They don't realise that not everybody wants to take a look at, or cares about, the source code.
They do realize that. They never state everyone should look at the code, they state everyone should have the right to if they want to. If you want to never come accross the source code, you can pay someone to do so for you. You do when you buy a Windows license, and you do when you donate to a FLOSS project.The_French_Rat wrote:A bit off-topic, but one reason I dislike the FSF: They don't realise that not everybody wants to take a look at, or cares about, the source code.mrugiero wrote:I don't think they care about the architecture used, it's far more along the lines of what Z98 said. They are against proprietary software, and ReactOS is neutral about it, and one of the biggest reasons to use it is if you depend on some closed software that isn't ported (otherwise, you could theoretically port it yourself), so they probably see it as promoting the use of proprietary software.
And where is the hypocrisy? They chose the UNIX architecture, but surely they didn't choose a closed source license. They chose something that worked and made a free implementation. They now have something that works, so they don't feel the need to reinvent the wheel, and that makes sense, priority wise. If your organization is about free software, but not about a specific way of working, the priority is having a system you can use that is free. ReactOS wouldn't be a priority in this scenario for the basic fact that it is a different way of doing things for which they already have filled the niche. People who support ReactOS will consider it a better way, of course. But better is not necessarily the priority, when you can already work with what you got and there are several areas where you are lacking. For the OS POV, the FSF mission is already accomplished, we've got a usable, working implementation of an OS that enables you to work virtually in every scenario. Is it the best? Certainly not in every scenario, but it still provides the basic functionality needed.Konata wrote:They do realize that, they specifically say people who can't program can still feel assured that those who can are able to review and modify the source, whereas with proprietary programs you're stuck with what you've got, spyware and all.The_French_Rat wrote: A bit off-topic, but one reason I dislike the FSF: They don't realise that not everybody wants to take a look at, or cares about, the source code.
Though on-topic, I do think it's a bit hypocritical of the FSF, as GNU was only meant to be a Unix because it was the most popular thing, and several people have said it would probably have been NT-based if it were started a few years later.
ActuallyKonata wrote:GNU was only meant to be a Unix
and many of GNU packages run happily on other platforms. Even the kernel, heart of the OS, was supposed to be different, but things did not happened this way. So we got a more conservative-one, rather than a revolutionary-one. Is it good or bad is anybody say, but, as mrugiero points out, it is already here and do a (good) job, so no point to waste more time on that. Especially since FSF have a bitter experience with the delays in the development of the other, "real", kernel.GNU's Not Unix
oldman wrote:I have come across this FSF website and ReactOS is not listed there. Would it be of benifit to the ReactOS project if it were!
I agree with most of your post, but I'm not sure if the GNU name as GNU's Not Unix is meant as "we don't follow the Unix philosophy/standards" but rather as "this is an independent implementation of a Unix-like OS with some freedom to vary some things, and a lot of freedom to be modified". More like a statement made to point out there was no copyright infringement and that it was free software. Again, maybe I need better history lessons, but that's how I always thought it was meant to be read.fred02 wrote:ActuallyKonata wrote:GNU was only meant to be a Unixand many of GNU packages run happily on other platforms. Even the kernel, heart of the OS, was supposed to be different, but things did not happened this way. So we got a more conservative-one, rather than a revolutionary-one. Is it good or bad is anybody say, but, as mrugiero points out, it is already here and do a (good) job, so no point to waste more time on that. Especially since FSF have a bitter experience with the delays in the development of the other, "real", kernel.GNU's Not Unix
Finally, *nix services can be run on top of NT kernel, so the rest of the GNU packages can, potentially, run on top of ROS with (minimal) modifications. The implementation of such a system is left as an exercise to the reader.