Can Microsoft Out-Google Google?
faria24 writes "For the past decade, Microsoft has largely ignored the Web as an emerging platform for application development with fears that it could render Windows obsolete. But that will all change next week, as Microsoft unveils a new strategy for transforming its Web properties into an open platform for developers. As part of its new 'Web 2.0 Platform' strategy, Microsoft will expose application programming interfaces, or APIs, for MSN Search using SOAP. MSN Virtual Earth, Desktop Search and MSN Messenger will all be opened up for outside developers to extend." Coverage on CNet as well. From the article: "Microsoft's online rivals, notably Google and Yahoo, already provide the hooks that let third-party Web developers write applications that tap into their Web services, such as search and mapping. Because these Web applications rely on a Web browser, they can, in theory, run on any operating system.
Microsoft, meanwhile, has always drawn third-party developers to Windows. But even with its commitment to Windows, analysts said, Microsoft needs to more fully address the growing popularity of online Web development. Having a healthy ecosystem of third-party add-on products helps drive traffic to Web properties. "
Wouldn't Microsoft have to actually come out with a web tool that people use that Google didn't already have to even have the possibility of that description?
Nope. Its a matter of trying to cut off each other's revenue stream. If MS takes eyeballs from Google products then Google receives less advertising revenue (which is their bread and butter revenue stream). If Google can produce pivotal applications that don't require MS OS or applications to run then MS (in theory) would receive less revenue from selling operating systems and applications (which is their bread and butter revenue stream).
This looks less like a battle of "what can I build to make more money" than "what can I build to fark my competition."
--- VERY IMPORTANT NEWS - VERY IMPORTANT NEWS ---
Microsoft, the most innovative company in history is about to embark on a bold new way of doing things. They are going to open up the APIs for their search engine (that noone uses), their messenger service (that noone uses), and their Desktop search service (which surprisingly, nobody uses).
Oh wait a sec, this just in... they're going to open up the APIs for Windows users only.
Of course, Google and Yahoo, whose services people do use, opened up their APIs sometime around 1997.
--- VERY IMPORTANT NEWS - VERY IMPORTANT NEWS ---
They can certainly copy the visible parts of Google, the products that are out (heh, mostly in beta) now.
But what about all the other stuff that's still hidden, that's in the Google pipeline? You could call it the Google Iceberg. The cool stuff that is yet to come. It looks like Google is pretty good at staying ahead by innovating.
As always, Microsoft is claiming to innovate, while actually just copying what they find out there in the marketplace already. They don't move the ball forward, they just keep the pressure on.
For all relevant details and discussion, see "Netscape".
Be very wary of it being a real 'fair and open' kind of competition thogh... in the same way that MS tried to taint and skew Java, Javascript, CSS and other web technologies, you can be pretty sure that this 'open' web 2.0 scheme will ensure that you develop for use only on IE (which still doesnt fullort support a multitude of W3C standards), with a long term aim of steering you off of a dangerously open platform standard such as a browser, and back into the Windows OS proper (where you can be safely contained and gradually bled of your cash).
Just as irrigation is the lifeblood of the Southwest, lifeblood is the soup of cannibals. -- Jack Handy
Actually, he never said that, though the GOP managed to convince many people that he did.
http://www.snopes.com/quotes/internet.asp
I just spent the last two weeks building a replacement Microsoft's ADO/DAO in our product using sqlite. Why? Because on rolling out we discovered that ADO would fault on half the machines, and DAO would fault on the other half of the machines. Weird error messages. Strange unrelated machine problems. Both implementations ran fine in the lab, but in the real world they would fail. Who has time for that?
So we ripped out both and replaced them with a brand spanking new sqlite version. Wasted a lot of programming and testing time, but it was the only way to make sure that our program would work in the real world. In a similar vein, we had to remove all the Microsoft calendar controls from our product because some of the machines in the real world would fault. Working around Microsoft's problems is not what programmers should be paid for.
Now, given a choice between Google's products, which are generally stable and just work, and Microsoft's API which will potentially lead to a lot of uncomfortable surprises on rollout, which would I choose? It's a no brainer.
No thanks, Microsoft, but you had your chance. When we got to the point that we had to set a policy to minimize the use of Microsoft controls as much as possible you lost any chance of ever getting us back in the fold.
The baby's fine -- please stop sending business cards.
I'm afraid the API's really are not open. They're open only under very restrictive licensing that very specifically prevents the developers from releasing an updated version of the Microsoft tool with the developer's desired features added.
Microsoft has also been caught, repeatedly, including unpublished operations in its kernels and its software that do specific functions much faster than the published API for those functions. It's fraudulent and deceitful and monopolistic to do so, since it's like having a secret back door for your airline that lets your customers skip going through customs, thus making your overall trip time much shorter.
Microsoft isn't the sweetheart of the developer universe anymore. Anything they offer now is too little, too late. Nobody trusts Microsoft anymore. And besides, would you want your "Web 2.0" apps to depend on Microsoft products and services? It doesn't take a rocket scientist to figure out that if you use Microsoft tools and API's, you're not going to end up with "web applications" -- you're going to end up with "Windows applications that are delivered via the web."
Around the turn of the century, the phrase everyone was spewing was "whoever controls the browser, controls the Web." Microsoft proved that this isn't true. They had a near-monopoly on browsers for years, and they blew it. They just let the browser stagnate while they went back to focusing Bill Gates' pet projects, like tablet computing and putting a database in the filesystem. Now Google is finally realizing the Netscape dream of turning the web into a pervasive computing platform, and suddenly Microsoft has to go into react mode again. Microsoft does not innovate. Microsoft reacts. And Microsoft gets pissy whenever someone other than them starts succeeding in the technology world. They're a bunch of spoiled brats. Is it any surprise that those of us who are building the next generation of applications are hesitant to go anywhere near Microsoft?
Tired of FB/Google censorship? Visit UNCENSORED!
Google has something that Microsoft doesn't - a brand name that's used as a verb. I don't care how much money you have, nothing beats having Jessica Simpson say "I googled for it" on national TV. Having a brand like this means that you have all the free advertising that you want.
If you don't want crime to pay, let the government run it.
Intelligent, forward-looking politician works for years to fund and shepherd through a new technology before anyone else has ever even heard of it
I don't know who to blame -- the character assassins who managed to get an incompetent leader elected over a competent one, or the American public who fell for it, twice. But either way, our nation is a poorer place for it.
I don't care if it's 90,000 hectares. That lake was not my doing.