There was one and now there is two
This page is going to be a collection of my observations on the MSFT war with GOOG. By my opinion, the most important event shaping the IT in the first half of the 21-st century. So the ‘*’ character on the title of this page: MSFT*GOOG, means a “sparkle” or more like “explosion”.
One of the very interesting observations (someone has made) is based around : Where is the Google coming from ? Today, in 2010 we are definitely not asking this question, but it is what must be on Steve B’s mind all the time, as recently as 2-3 years ago. How can such a big beast, sneak under the radar?
Very simple: no one took it seriously. Neither importance of providing omnipresent search infrastructure of the WWW, neither the validity of the Google business model. Thanks to this overlook, I am sure that we all have to be thankful to Google, because everything that has to do anything with new software on the web, is being read by someone who works for someone.
2010-04-26
GOOG Chrome OS will (90% probability) make it not possible to use another browser. That means a Google client device will have a Google browser, and no other browser will be possible to install on that device.
You know how in Chrome OS video Google says: “..Just Your browser…” ?
Well I am afraid that the GOOG “subliminal message” is going to be: “Just OUR browser”
So far GOOG is not forced, even to think about “giving the browser choice to the consumer”. I wonder when (not if) is EU going to notice this >:o)
2010-05-13
How could I resist referencing this image, from otherwise poorly researched article 
GOOG (bang) MSFT
It is poorly researched because it failed to spot (and list) all the weapons MSFT is readying for full-on-frontal assault on the GOOG cloud.
I am primarily talking “AZURE” here. GOOG has nothing like “AZURE”. MSFT has accumulated 25+ years of armies of software developers behind it. And “AZURE” is one fleet of high-tech asault vehicles, which are going to transport wave after wave of loyal MSDN armies, together with their new and legacy software, all the way to the MSFT Cloud.
I do like HTML5, JavaScript, JSON and the rest. But somebody has to do something on the server side. Or in todays politicaly correct speak : “on the Cloud”. “AZURE” is the MSFT’s key to moving everybody and everything “up there” a.s.a.p.
Can anybody tell me what is the GOOGy’s response to “AZURE” ?
2010-07-08
I swear to You, I never ever read MSFT eula-s , or otherwise, but for some unexplicable reson , I opened :
Microsoft SharePoint Designer 2007 - English.rtf. A file which is coming with SharePoint Designer 2007. And there in those deep depths of the ocean of MSFT I found this pearl of MSFT wisdom :
12. LIMITATION ON AND EXCLUSION OF REMEDIES AND DAMAGES. You can recover from Microsoft and its suppliers only direct damages up to U.S. $5.00. You cannot recover any other damages, including consequential, lost profits, special, indirect or incidental damages.
This limitation applies to
• anything related to the software, services, content (including code) on third party Internet sites, or third party programs; and
• claims for breach of contract, breach of warranty, guarantee or condition, strict liability, negligence, or other tort to the extent permitted by applicable law.
It also applies even if Microsoft knew or should have known about the possibility of the damages. The above limitation or exclusion may not apply to you because your country may not allow the exclusion or limitation of incidental, consequential or other damages.
Ah, this realy made my day today Imagine a company whose future depends on beating Google, and, which is packaging it’s developer friendly free tools, with this kind of eula-s.
I have yet another subtler example of how MSFT still , does not understand fundamentals of the batlefield with Google.
Now, can You really imagine anyone in Google leaving this kind of message in their software?
So wrong, on so many levels. In one single message embedded in a software. This is what I am calling : Pure art.