Slashdot Mirror
What's the Business Case for Microsoft and Open Source?
Friend of perl developers everywhere, Jeremy Zawodny, has an intriguing question: "If you had to explain to Microsoft why they should change their
attitude toward Open Source, what would you say?" For more about this, read on...
From Jeremy: "If you had to explain to Microsoft why they should change their
attitude toward Open Source, what would you say? More to the point,
how can Microsoft benefit from better supporting or even adopting
Open Source in their business? (Replace IIS with Apache, for
example.) Does it make sense for them? Are there ways that they can
use Open Source as a competitive advantage without pissing off the
Open Source community in the process? Which of their products would
make sense on Open Source platforms? How can the Open Source
community help Microsoft? Or is this a lost cause? IBM has made it
work. Can Microsoft?
I ask these questions because I may have the chance to talk with folks at Microsoft about Open Source. And it only makes sense that I look to the community for input. So let's hear it. Flames won't help. Thoughtful answers and ideas very well could."
As a guy who has to support IIS in mission-critical apps, I'd have to say that it would give them a lot of credibility in the enterprise if they opened the source just for IIS, for starters. At least once a quarter, somebody in our organization asks why we're not using Apache yet, and with the IIS security problems that crop up all the time, it's getting harder to answer that question.
I know what their answer is going to be, though. They don't want to open up IIS because it will expose all of the existing installations to attacks until patches are written. They'd rather keep it closed to protect the morons who don't apply patches than to open it up to fix the rest of the holes.
What's your damage, Heather?
- score -1, naive
- score -1, simplistic
This is a serious proposition and about as objectively applicable as "-1, Troll"Linux can. Linux can .Use Linux
That Linux can! That Linux can! I do not like that Linux can!
Do you like open sourcing plan?
I do not like that Linux can. I do not like the open sourcing plan.
Would you like to free source share?
I would not like to free source share. I would not like it anywhere. I do not like open sourcing plan. I do not like that Linux can.
Would you like it very stable? Would you like it to enable?
I do not like it very stable. I do not like it to enable. I do not like to free source share. I do not like it anywhere. I do not like the open sourcing plan. I do not like that Linux can.
Would you use it in a X-Box? Would you use it if it ROCKS?
Not on X-box. Not if it rocks. Not if very stable. Not to enable. I would not let them free source share. I would not let them anywhere. I would not allow open sourcing plan. I do not like that Linux can.
Would you? Could you? In your biz? Use it! Use it! Here it is.
I would not, could not, in our biz.
You may like it. You will see. You may like it if it's free!
I would not, could not if it's free. Not in our biz! It should never be!
I do not like it on the X-box. I do not like it that it rocks. I do not like it amongst our biz. I do not like it that it is. I do not like they free source share. I do not like that anywhere. I do not like that Linux can. I do not like you Linux man!
service! service! service! service! Could you, would you, as a service?
Not as a service! Not if it's free! Not in my biz! Man! Let not it be! I would not, could not, on a X-box. I could not, would not, if it rocks. I will not use it if its stable. I will not use it even to enable. I will not let them free source share. I will not let them anywhere. I do not like open sourcing plan. I do not like that Linux can.
Say! if in copyleft? always free copyleft! Would you, could you, copyleft?
I would not, could not, in copyleft.
Would you, could you, why so nervous?
I would not, could not, I'm NOT nervous. Not as copyleft. Not as a service. Not in my biz. Not if it's free. I do not like that it can, you see. Not if it's stable. Not on X-box. Not to enable. Not if it rocks. I will not let them free source share. I do not like it anywhere!
You do not like open sourcing plan?
I do not like that Linux can.
Could you, would you use what we wrote?
I would not, could not, use what you wrote!
Would you, could you, to avoid your bloat?
I could not, would not, avoid bloat. I will not, will not, use what you wrote. I will not compete with them as a service. I will not because it makes us nervous. Not in our biz! Not if it's free! Not if it is! You let me be! I do not like it on the X-Box. I do not like it that it Rocks. I will not use it if it's stable. I do not like that it does enable. I do not like they free source share. I do not like it ANYWHERE I do not like open sourcing plan!I do not like that, Linux can.
You do not like it. So you say. Try it! Try it! And you may. Try it and you may, I say.
Man! If you will let me be, I will try it. You will see.
Say! I like open sourcing plan! I do! I like that, Linux can! And I would use it because it's stable. And I could use it to enable...
And I could charge for providing a service. And I could copyleft without being nervous. And in my biz. And still source free. For you can still charge for a service fee!
So I will use it on the networked X-box. And I will promote it because it ROCKS. And I will use it because it's stable. And I will use it to enable.
And I will use it here and there. Say! I can use it ANYWHERE!
I do so like open sourcing plan! Thank you! Thank you, Linux man!
By The Cat with the RedHat
It seems to me that Linux and open source are classic disruptive technologies. In this case the technology is not the OS itself (anyone here who can't name a dozen OS's in one breath?) but the GPL, the development model, and the worldwide linking of motivated developers into a slightly-cohesive competing co-operating group.
The GPL has provided a framework whereby a self-sustaining body of software has come into being. The body of developers don't rely on traditional business models to sustain themselves.
If Linux and open source become at all successful Microsoft is going to lose billions of dollars in revenue. Heck, they probably already are. I'm suprised they haven't sent the boys around to break RMS' and Linus Torvalds' kneecaps or roll over them with a bus.
This is a 'company' or community MS can't fight using traditional business models. They can't lower their prices enough to beat free. Many of open source products are at least of equivalent quality to MS products.
They've tried running attack PR campaigns, but to some extent attacking open source is as hard as attacking any other community spirited organisation, such as (for example) the Scouts or Guides, and all the bad press has so far rebounded on MS, it's a bit transparent after all. And how do you effectively attack people who are giving things away for free? It's like trying to claim that "Meals on Wheels" volunteers are evil because the food they deliver sometimes isn't absolutely perfect.
As an aside, I was in the Science Museum in London a few years ago and I saw a gas-fire powered room fan. The idea was that when it got too hot in summer, you lit this gas-fired engine and it turned a fan to blow (now warmer) air around the room to cool you down. It was a last trump of the old monopoly gas companies trying to show their product was as versatile as the new-fangled electricity. It shows the lengths an old monopoly would go to, to try and preserve their old business model in the face of a disruptive technology.
So, in a possibly vain attempt to get back on topic... I'll be interested to hear what you have to say. Because I feel only one of a few possibilities can actually happen. One is that open source limps along as a permanent embarrassing cousin to shrink wrap proprietary software. The other is that it more or less displaces shrink wrap commercial software.
My money is on the latter, and for a simple reason. MS has sent many companies down the tube by the simple expedient of knowing that the other company will eventually make a mistake, and then they are dead. MS has made many mistakes too - but the synergy of owning the OS and some popular apps meant they've had the revenue to recover from them, whereas companies reliant on a single app only had to trip once and they were gone.
Now the tables are turned. Open source isn't going away. If it can survive and get to where it has now, on an insignificant market share and difficult to use products, it isn't going away now it has growing market share and great things like KDE3 and Moz and GNOME and open office and so on that stand up against MS' core products.
Now it's MS that has to avoid making mistakes.... In my view that classic mistake they are making is concentrating on their market share and revenue rather than the customers. Look at the PR and mindshare disaster that Licencing 6 has proven to be. Just goes to prove the old saying that once a monopoly finishes dealing with it's competitors, it starts beating up on its customers.
MS contains some of the greatest developers in the world under one roof, probably THE greatest number of developers working for a single company. The problem is that so much of their work seems to be directed towards a 'scam' - keeping MS on top and killing other companies, rather than just turning out great products. It's proven a very effective strategy so far, the issue is can it survive against a community who isn't playing the same game?
So what can you say to MS about open source in general? It'll either eat them or live alongside them. Either way, they lose. And it's as inevitable as what happened to the horse and cart when the automobile was invented, and nothing they do can really change how this game is going to play out economically. So they may as well ignore it and hope it'll go away.
I c# went totally open source, it would at least have that over Java. In my experience 95% of developers have a negative attitude toward M$, and making c# open might help with this. I think developer opinion is important because they often choose which products/languages to use. Personally I would never choose M$ development languages over Java because of the closed/platform dependant nature.
What's needed is a change in the way MS developers think, with this I mean the people using Visual Studio etc to build solutions for the MS platform. If they start adapting Open Source more, then THEY will start pushing MS. With most MS platform developers being used to buying, and selling, their apps without source code and with a restrictive license, there's no demand on MS at the moment to go Open Source.
However, it's not likely to happen as long as Open Source is pushed by zealots (*cough* RMS *cough) who have nothing to say about MS (or M$) apart from some rant about how they suck, preferably in 1337 5p34k.
There are a lot of gains from sharing source and solutions, but, that culture just doesn't exist in the MS platform developers mind, thus there's little pressure on MS to even consider it as a policy.
Wax-Museum Fire Results In Hundreds Of New Danny DeVito Statues
open source != free as in beer
open source != free as in speech
Open source means the source is open, yes, this means it might be used without permission. open source to me is sharing information, not giving away work for free. Allow people to view the sourcecode, but license and charge for the app.
Mostly like any HTML page is today. Design theft occurs occasionally, but still there are plenty of people who pay web developers to build a site for them. If HTML code was compiled and unreadable, what would the web be today? Didn't most of us learn website coding by copying HTML/CSS/Script snippets from other pages? Has the webdesign industry died because of it?
Problem is, we (as in MS developers) are used to HTML being open source, but anything else must be hidden or someone will steal it for sure!
We need a change of culture and way of thinking is all.
Wax-Museum Fire Results In Hundreds Of New Danny DeVito Statues
It's hard to know where Microsoft would benefit from Open Source (remembering that they can already, ahem, borrow BSD'd and similar code) without knowing how much each product contributes to the company financially and how much each product costs, but, if I were to hazard a few guesses, it would be these:
1. IIS==>bit bucket
IIS does not dominate its market and has a wretched reputation. IIS extensions are available under apache, and the apache license would allow Microsoft to make its own proprietary extensions to a Microsoft-supported license.
It would make a world of sense for MS to bite the bullet, declare apache their web server, and add MS-only content in the form of proprietary mods.
2. SQL Server.
Big asterisk here. If SQL Server contributes serious net dollars, I might continue to ride it for a while.
However, SQL Server faces fierce competition at the high end from Oracle and DB2. The continued visibility of Open Source is exposing it to danger in the middle from solutions like PostgreSQL and MySQL, products that conspire to take the profit out of the segment.
I can't help but think that Microsoft could learn something here from the tremendous success of Access. Nobody buys Access because it's a great database. They buy Access because it's a database they can use. Microsoft can open up SQL-Server or they could even get more radical:
base a new database on PostgreSQL, perhaps with extensions to ensure that current SQL-Server databases are cleanly supported.
Then, without having to R&D the database (and, not coincidentally, gaining a marketing point in terms of customer flexibility), focus on proprietary tools that make developing and admining the thing easier. Maybe special additions (as separate proprietary products) to help exploit the Windows platform.
3. The Access back-end.
As I said, nobody buys Access because it's a great database.
4. Outlook Express.
A little danger here, because it might make it easier to clone Exchange. However, this could be a sort of "reverse-samba": Outlooks showing up in all kinds of strange places and on all kinds of strange platforms where it never lived before. Why? PHBs. Nuff said.
5. NetMeeting.
C'mon, guys. The whole purpose of NetMeeting is to let people in remote locations participate in a meeting. MS doesn't charge for the basic client, anyway. Opening this means that Windows can communicate with anyone else using the NetMeeting softwareThis one seems like a no-brainer, especially as a revenue stream might be found in enhanced software for originating sites as opposed to mere participants.
6. Whatever MS calls it's instant messenger.
That would be a great stab at Yahoo and AOL, and, for MS, wonderful irony.
Anyway, those a re a few of my ideas.
Microsoft needs to change its attitude towards Open Source for the same reason that the dinosaurs needed a near-earth asteroid search.
Unfortunately for them, they are as likely to understand Open Source as the dinosaurs were to understand the technology necessary for a near-earth asteroid search.
Unfortunately for us, the analogy is also likely to work in that it took the dinosaurs hundreds of millions of years to go extienct, and similarly Microsoft is likely to be around and dominating the planet for some time to come....
-Rob
3. The Access back-end.
As I said, nobody buys Access because it's a great database.
Yeah, and they'll never improve that back end because it drives sales of SQL server. Let me make this perfectly clear: making Access a better product would cannibalize sales of SQL Server, so MS will never make it good
Making good products is at odds with market segmentation. This is one of the fundamental benefits of free software- there is no market segmentation for code so the perfect never becomes the enemy of the good, as we see in the Access situation.
microsoftword.mp3 - it doesn't care that they're not words...
I'm not quite sure who you will be talking to and what exactly you mean, but if you're talking to the programmers, prepare to be surprised at the attitude. I was a contractor at Microsoft. What language did I program in? Perl. While there, I worked alongside Linux advocates and other free software fans. I heard more Windows bashing there than I have at my non-M$ jobs. The programmers there are geeks. They're likely to already agree with you.
Now if you're talking to the marketing or legal departments, good luck. I don't know if they can even turn on their computers.
It is not in Microsoft's interest to change to open source. They have a tremendously successful business model making them one of the richest companies in the world. They are the sole-source supplier for the most popular computer software in the world. There is no rational reason for them to switch to selling and/or supporting open-source software.
Sure, we can all bitch about Microsoft products' security holes. We can gripe about performance and architectural issues. And many of those complaints are valid ones, but Microsoft is not in business to produces the most secure, high-performance, well-designed software in the world. Microsoft is in business to make money -- which they do very well.
The only rational points to argue are:
1. Microsoft's continued attacks on the open source movement are damaging their credibility and hurting their customers, many of whom want to integrate open source products into their Microsoft networks.
2. Microsoft's data storage and transmission formats should be opened up to allow value-added third-party vendors to produce products that use and manipulate the data. All that leaving the formats closed accomplishes is a delay while third-parties reverse engineer them.
3. Continued battles with the open source community are going to result in more public outcry for anti-trust action.
4. Microsoft has a PR problem right now due to their insistence on software audits at cash-strapped school systems, security holes, the Justice Department case against them, etc. Extending an olive branch to the open source movement might help reduce that PR problem.
Above all, remember that Microsoft is a for-profit business. They aren't going to get teary-eyed when you tell them about the comaraderie and inspiration that you feel when working on open-source products. They don't want to be part of some big, happy family. They want to rule the world.
IBM has changed its business model: they no longer sell software products; they sell a "solution to a problem", which they use some of their own software products to solve. They provide a service, which is what their customers need, and it provides them with steady, subscription-style income that fosters a better and more honest relationship with their clients than the hit-and-run attitude developed by salespeople who only need to sell a product once. Plus, because it's clear from the outset that they're going to be selling a service, customers don't get pissed off (as they do with Microsoft) having to pay continuous fees. Make no mistake, both companies charge continuously: however, Microsoft charges for support (which gets people pissed off -- the product is supposed to work without help!) while IBM charges for the service (which includes support when things go wrong). It's the same thing, but with important psychological differences on both sides.
Microsoft is already seeing the value of selling services rather than products (spurred by the success of subscription-based AOL) and is slowly moving to software-as-a-service. However, their legacy of selling expensive products is making software-as-a-service very unpopular with their customers, who see it only as a way of charging many times for a product they used to buy only once. By changing their model to being entirely service-based, they would be free to use open source wherever it happened to be better than their in-house solutions (e.g. Apache) without it costing them any revenue. They could then contribute to the open-source products they use just like everybody else does.