Linked by Thom Holwerda on Thu 23rd Jul 2009 09:43 UTC
Microsoft Sometimes, some things are just too good to be true. Earlier this week, Microsoft made a relatively stunning announcement that it would contribute some 20000 lines of code to the Linux kernel, licensed under the GPL. Microsoft isn't particularly fond of either Linux or the GPL, so this was pretty big news. As it turns out, the code drop was brought on by... A GPL violation.
Thread beginning with comment 374864
To read all comments associated with this story, please click here.
Proprietary Software in General
by hackus on Thu 23rd Jul 2009 15:37 UTC
hackus
Member since:
2006-06-28

Is closed because there are massive internal violations of software patents and more than likely scarfed GPL code.

Remember Linksys?

The FSF had to serve formally CISCO to get them to cough up the code.

http://www.fsf.org/news/2008-12-cisco-suit

What we really need is to fundamentally destroy all commercial interests in proprietary closed software. The best way to do that is through the following means:

1) Actively organize your organizations I.T. department to seek out and identify Network, Storage and Applications which have open source equivalents and demand they implement them.

2) Once these substitutions are identified, eliminate the ones you feel are to risky at this point, and implement as much as you can in Open Source/GPL.

3) Restructure your department. If you have a bunch of Microsoft Certificate guys who do not want to adapt to save costs using GPL software, replace them with people who have 4 year degree comp sci degrees or who have demonstrated expertise in open source software.

4) Sponsor a Open Source project specific to your business goals. Are you an ISP? Tired of high priced CISCO routing gear? Use a different vendor who is friendly to open source, or better yet, build your own routers. The following projects would be a great place to start with either money or staff time:

http://www.quagga.net/

Patronize these vedors who do 10GE for Linux for example:

http://www.myri.com/scs/download-Myri10GE.html

Essentially what will happen if you do these things will be the following:

1) Proprietary vendors will simply cease to exist.

2) Customer service should be improved because the customer will probably be involved in the project and also has a stake in it to succeed. Whether it be a networking product as in this example or something else.

3) Quality will be transparent. Your customer will see it, your engineers will see it, and so will your vendors.

It is incredibly hard to engineer crap that people can see, who also buy.

Proprietary Hardware Vendors and Proprietary software vendors are absolutely terrified about this particular outcome of open source. They do not want you to know where they cut corners, because a big unknown like this prevents you from doing any sort of cost analysis.

It is time for proprietary software to GO AWAY.

One more thing. Get rid of support contracts, they kill budgets. I tell people that support contracts for proprietary software are there because they are defective, number one. Number 2, organizations that have support contracts have no incentive to create quality software.

Would YOU create quality software if your revenue depended on $500 a month or $200 bucks a incident?

Of course not. Open Source transparency generally yields better uptime, and when there is down time, its usually nothing major that you would need a big expert to fix. After all, you have engineers you have on salary onsite, that can look at the code and figure it out and implement their own fixes.

One of the most spectacular declines for example in the proprietary world, is in the business exchanges of the world. What happens when a stock exchange goes down?

Well, if your like Londons Stock Exchange, too MUCH happens.

http://techgeist.net/2009/07/london-stock-exchange-moving-windows-l...

Of course, you can still opt to outsource support for Open Source just like Proprietary Software. Thing is, its your choice who gets the money. You can spend it on your staff, or you can ship it out of the organization.

Please Help by following the above guidlines and indeed, given enough time, proprietary software will go away and the world will be a better place.

I know it will make my job much more pleasant with my customers and coding will be much more fun!

-Hack

Reply Score: 1

microsys Member since:
2009-07-23

Someone is a bit full of oss here ;) ( i will comment the news a bit down ;) )
I do like OSS very much, i am even a bit active in programming there, but i do not think OSS is the answer for every software available. A lot of applications can be replaced by oss, but with heavy disturbance in workflow or similar... It is possible to replace it if you do not need every feature in the closed version. Or you can replace it one app by 3 oss aps, which do the same. But it makes it a lot more complicated for the users.

So as long as a lot of the OSS Apps are designed and implemented from a developers narrow view without having feedback with inhouse use or wide professional use at production which can point out where the design needs to be changed, they will not be a fully countable alternative. Also the decision process takes some times to long or is steered in the wrong direction by the maintainer(s) since he does like the feature. A lot of OSS Apps are not focused on providing a comfortable work flow but pressing as much features available in or being defaulted to the already seen UI.

I have to say there are some exceptions, which i accept open hearted.

There is one more problem within the interoperability within the different alternatives or "alternativ collections". There are sure a lot more operabilities inbetween groups or versions of applications, but the overall communication between different OSS apps sometimes really gives you a burdon. Even more problematic is the users need to accept the new system and especially ppl you have a long time in your company can have problems with adopting to new systems or completly different workflows.

So you want them to just get fired and take some other guy, then i have to say i am happy i am not working in your company if your play with the "life" of your employees like this ;) .

i just thought to tell that ;)

PS: I would appreciate if there would be even more OSS Software which were real alternatives to some closed source apps, but i think there will always be a market for closed source ... always!

PPS: Just one example: Collaborative Software (Exchange, Kolab Mailserver, OpenXchange, .. ..). And do not come up with the "Webserver packed" Colabs like egroupware, .. .., they are no real alternative. I tried, believe me ;)
They are quite usefull, but not in full production system which need a lot of "luxury" features and "Easy to use" widgets having fast response times on their clients. And native running apps will most likely have a faster response time than an browser based collab client system.

PPPS: For the news i think it does not weight that much what makes them release a part of code under the GPL but that MS does release it at all under GPL. Even if they were forced to. To do this without a big comment or trying to get around it is something what nobody was expecting from MS. I think it is a small step to a more open future ;)

PPPPS: But Vista is still crappy ;)

Edited 2009-07-23 16:18 UTC

Reply Parent Score: 1

microsys Member since:
2009-07-23

I forgot.

There are a lot of oss apps i do not want to miss. These can be replaced by closed source, but the workflow will also be gone. I all comes down to:

REQUIREMENTS

Reply Parent Score: 2

Karitku Member since:
2006-01-12

Posting links to sites that stories are based on Steven J. Vaughan-Nichols article is like putting shit in brown bag, it's still shit. LSE still uses .NET based system, Steven J. Vaughan-Nichols is still freetard number 1, this has nothing to do with Cisco case, propierity software isn't dying thank god since there is enough unemployment in world and world keeps spinning around sun. The END.

Reply Parent Score: 0