4 ms·
From their webpage: "Nearly ten years ago the ReactOS Project released version 0.3.0. Today we are proud to announce the formal release of version 0.4.0. ". Th
by simonebrunozzi 11y ago
From their webpage: "Nearly ten years ago the ReactOS Project released version 0.3.0. Today we are proud to announce the formal release of version 0.4.0. ".
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.
- outworlder 11y agoMaybe I've missed the sarcasm? GSOC is for FOSS projects only.
- viraptor 11y agoLinux went from 2.6.0 to 2.6.39 in 8 years. That's not even 0.1 change! It can't be commercially successful... </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?
- chrisweekly 11y agoRe: version numbers and context: Hear, hear! High time to decouple marketing releases from software api versioning. Eric Elliott says it better: ): Major.minor.patch (: Breaking.feature.fix https://medium.com/javascript-scene/software-versions-are-broken-3d2dc0da0783#.7ujofs3b4 https://medium.com/javascript-scene/software-versions-are-br...
- viraptor 11y agoThis doesn't apply to Reactos though. The api is "whatever windows is doing". Unless they remove something supported by windows N-1 and instead implement replacement interface from windows N, there's not going to be a "breaking" release. But as far as I know the API target is not going to change for a while - it's 2003 kernel / 8.1 user.
- simonebrunozzi 11y agoI really don't understand why the downvotes. Can someone explain?
- reitanqild 11y agoAs outworlder pointed out being commercially successful does not seem to be a requirement to be accepted for GSOC.
- pjc50 11y agoIt's a software freedom project, so commercial success is irrelevant.