ReactOS was selected for Google Summer of Code 2016
reactos.ru
reactos.ru
Agreed, but not everybody's seen the light, aka POSIX.
I also view ReactOS as a way to subvert Microsoft's control over users and developers who enjoy aspects of Windows-like operating systems, such as the UI or the APIs.
Think of all the weird desktop apps, custom databases, etc. that small businesses, schools, and other non-technical orgs have baked into their workflow. Yes, eventually we'll have wonderful legacy-free versions of all of these available on the web but in the meantime wouldn't it be nice to give them some outlet to use them w/o paying an MS tax or dealing with the infinite upgrade treadmill?
It's not even free. New computers still pay licenses for windows 10. The "free" upgrade offer ends in July.
So far it is in the alpha stage and needs to go to beta stage soon. It only has a 48M overhead and loads faster than the real Windows. It has EXT file system support as well as FAT support but NTFS is read only.
Someone can make a ReactOS bundle with PHP, MySQL, Apache2 so it can be used as a web server. If someone ports CLRNET or the Dotnet open source programs over to it, it can run ASP.Net stuff as well.
There isn't much point in throwing a massive amount of resources for building an AMP hosting environment. If somebody needs to start an AMP server from scratch and he really needs to save money, there is LAMP.
The only realistic use case of ReactOS is large-scale deployments of machines which need Windows (driver) compatibility, in which case ReactOS would save large amounts of money.
https://www.reactos.org/wiki/Google_Summer_of_Code_2016_Idea...
There is plan to do it, but from what I understand, it's still not available:
https://www.reactos.org/wiki/ReactOS_Update
Security is another major problem with this OS. They are proud to have produce 9M LoC, but they don't advertise how they assure this code is not full of vulnerabilities.
Do they audit the code ? Do they use static analysis tools ? Do they have specifics security practices and processes ?
I don't see any security advisory on their page. I only see a wishlist on their wiki https://www.reactos.org/wiki/Security
Among many other reasons why you shouldn't use it as your main OS. But not even the React Devs would suggest that you do, so I'm not sure what your point is. It's clearly still in the development stage and is almost certainly just going to be run in a VM for the time being anyway.
Also, there are countless document templates (which plague different work fields) that are utterly incompatible with Google Docs and break all over.
Don't extend your competitors platform. Chrome took IE users and made them Chrome users because Google's platform is the web, not the desktop. So Chrome has been pushing forward traditional desktop features such as offline, OpenGL, and sockets, to displace desktop software.
Look at what Apple has done with the iPad, they've been the market leader and MS has had to follow them, only recently shipping Office apps for iOS. They're blazing ahead with their own platform which serves their goals, not tired old legacy software from 30 years ago.
They might argue that we're spending more time in web applications, rather than purely in native desktop apps - This is reflected in their Chromebook offering, which largely strips away the non-web experience.
In the front page of ReactOS[0]:
> 9,000,000+ lines of code
> And growing!
Is the huge and growing codebase a pro or a con?
I wonder if the reason we haven't seen more work on ReactOS compared to Linux development is the commercial backing that Linux development receives from the big guys (Red Hat, IBM, et. al.) I wonder if people are wearisome of funding ReactOS beacuse of Microsoft.
You can see very often the pattern of "X was implemented using the library from Y, which works but not well" or "Y was implemented and working for Z case, but it's effectively broken" and so on.
I've seen comparatively little complaints of the kind "bl00dy Windows performs this functionality in an awkard and messy way".
I don't really have much faith in ReactOS, although I would really love to see it mature.
Following its evolution with the time, I can see clearly that it's a type of product which is doomed to be "90% functional" for its entire life (unless somebody will throw a massive amount of money at it).
While you could consider Wine to have the same fate, there is a distinction in the fact that Wine is more directed to a per-case basis, which makes the "90% functionality" state acceptable.
Even if it was done with a good and helpful intend. For a lot of people it's pure pain if you take control of the scrolling.
This
http://f.cl.ly/items/0Y3e3k3A17293r0s2y3d/Screen%20Shot%2020...
Actually, I was oversimplifying when I said I have JavaScript disabled. I’m actually using JS Blocker¹, which gives me your first sentence². Of course, the end user using a browser extension to gain that functionality instead of it simply being a part of the Web does nothing to actually encourage the creation of a “reach web”.
――――――
¹ — http://jsblocker.toggleable.com/
² — http://f.cl.ly/items/0q1m280M40290t222n0U/js_blocker.png
That's just pure rage. Why developer of that website even bothered with implementing (or using some library) to hijack mouse actions.
On this site the result was a total disaster: any attempt of scrolling made the site jump around randomly, and immediately stop right back at the start again, making scrolling with the mouse impossible.
This is a group of C/C++ hackers who have spent the past 18 years re-implementing Windows 95. The fact that there's any CSS at all on their website is a minor miracle.
I don't know how strongly I feel about non-responsive websites displaying a fixed header bar. However, I'm pretty sure that most people who do feel strongly about it either way aren't going to be using or hacking on ReactOS.
No more smooth scrolling!!!
This is the problem. Going from 0.3 to 0.4 in TEN years means that you cannot be commercially successful.
As much as I admire ReactOS' contributors and their efforts, I have little faith in their ability to make a dent in the market.
GSOC is for FOSS projects only.
</sarcasm> Version numbers don't mean anything out of context. Is there any specific issue you wanted to point out that took them too long to implement?
): Major.minor.patch (: Breaking.feature.fix
https://medium.com/javascript-scene/software-versions-are-br...