Different frequency of software releases

Oops, we mentioned a line about this in the previous section itself. Anyway, the mongrel finally manages to create his brainchild. He uploaded a downloadable and easy-to-install version of his extension on the Mongrella Flamewolf website. Within a span of about 30 nanoseconds, the new extension hits nearly 2,486,546 downloads backed by tons of comments and praises about the new idea. The mongrel thinks, “Insignificant and trivial idea, eh?”
Then suddenly, it hits a snag. Another mongrel yawns while in the middle of watching a Porno and then, the window closes. “Damn”, cries the poor mongrel who has to stream that movie in his super slow dial-up connection (Yes, dial-uppers will continue to exist even after the internet goes inter-galactic!). Out of anguish, he soon reports his case to Mongrella providing the URL of his porno. Not only did he get a downloadable source of that same porno, but also, the issue got some serious developer attention to it. Within no time, it became an issue of serious concern and got the title of a dysfunctional object, or in simple terms – It was called a “Bug”. And within no time, this bug was fixed in a completely new version, in which the ‘Yawn’ function is only applied in the case of Bollywood movies. (Yep, India’s population would swell enough that it gets a separate planet to live, and there too, Karan Johar movies won’t lose the release cycle pace that is competitive to Open Source Development.)

Given a large enough beta−tester and co−developer base, almost every
Problem will be characterized quickly and the fix obvious to someone. This statement is justified by the scenario above. New bug fixes, program errors are fixed by enthusiasts universally. It is the policy of releasing early, releasing more often and listening to the customers that is really commendable difference between the two standards.

Different Enough?

Different enough to stand apart? Different enough for you to take an adoption? Read on for more… We know how to get people convinced!

More on Open Source Software

Better for Coders

Open source software development is quite different from conventional closed source software development. Closed source software companies for example, let’s assume a fictional company by the name Microsucks, which follows a closed source approach to development and SourceGorge, which follows, ahem, the OSS law…
Read More

Better for Users

It had been a long time since the employees of Microsucks started a mutiny against its own company due to severe dissatisfaction after the development department came under a new guy by the name Gay Ozzie, who preached things which (you might guess out by reading his name!) had caused severe unrest in Microsucks.
Read More

Faster development

Future of Open Source

So where does it all end? How exactly will open source shape our lives leading us to a better tomorrow? It is for certain that with this level of growth and progress, we expect to see open source as the driving force of the software industry in the next few years.
Read More

Is Open Source a thing of the future?

No; Not at all. That’s as bad as saying we don’t have birds flying around. It’s not about having a different perspective here, it’s just a fact. Open source is here. Look around you, look at the browser you’re using, or the mail client you have open, the backend components of the website you’re browsing or maybe even the operating system you might be on.
Read More

Greater Freedom

As told before, SG sees developers in users. Following the movement that ‘rebels’ started in a distant planet Earth and following the guidelines they had set for building OSS, SG still continues its excellence in building better and better stuff for everyone.
Read More

Open Standards

Also known as Open Formats, Open Standards are much more than just a published specification for storing digital content, media or data. It is a key to freedom.
Read More