Skip to main content

The fight is in the open

Been busy lately and so have not managed to post for quite long.
But I just had to post this. This post is dedicated to all persons who dont know anything about the fight between MS and Google:
Check out the links starting from:
http://news.zdnet.com/2100-9588_22-5875433.html?tag=nl.e589

There are more links as you get thru the article. Be sure to read those too.

And just as a side-note: Check out "Atlas". These are client side and server side components, which easily (??) enable you to make Web calls. This is done by encapsulating AJAX. (please dont insult by telling me that you dont know what that is).

Comments

Rakesh Pai said…
Google and Microsoft are not competing, as most people would like to believe. In fact, they are not even on the same turf.

If they were competing, why would Google's latest killer applications that have got so much hype - Google Earth, Google Desktop Search, Google Desktop and Google Talk - all work on Windows only?

Microsoft makes operating systems and provides software resources and solutions at a price. Google provides free services to support its advertising business. It is two entirely different businesses with different interests, targetting two different market classes using two different revenue models.

It is appaling to see companies like ZDNet among others trying to generate hype out of nothing.
Sachin Nayak said…
Yes, I have been thinking about this for quite some time since posting this article. They do have their different markets. But i guess they do have an ego problem about sharing the top place with the other company, even if the company is in an altogether different area.

Of course, Google will not be able to enter the OS sphere so easily, or will it?
Rakesh Pai said…
Yes, they do have ego problems. It is evident by reading about Ballmer going around screaming "I will kill Google", which proves your point in a not-so-subtle way.

Google will form a "virtual-OS", or an "Internet-OS" as some like to call it, if I see it right. What this means is that you will eventually replace Microsoft's applications with Google's services to do virtually everything you used to do on a MS OS. When you take a traditional desktop application, put it in a browser, give AJAX style interfaces, do not lock in the user's data with proprietary formats, add remote accessibility to the bundle, add great online collaboration tools, and throw in platform independence, customers will see value, especially in a connected world like today's.

That is MS's greatest threat from Google. Google is not trying to be another MS, but it is definitely targetting becoming an alternative desktop. I think it has every reason to succeed!
Sachin Nayak said…
An alternative desktop...bang on target. I guesss that's what's gonna happen. not an OS but a desktop!!! hmm.. sounds extremely logical. But that means there is gonna be a performance hit somewhere.... server!!!!

Popular posts from this blog

So you have your website deployed in PROD ... now what ??

Posting on behalf of Usr.Web.Speed - My previous job had been to architect and develop websites for various customers. During that time my team and I have architected and developed various web applications mainly for enterprises. (But below info is not restricted to enterprises) Other than the usual development and testing tasks involved, our focus area was to abide by multiple SLAs. One of the primary SLAs was to provide the users of our websites a very low (usually subsecond) response time (or page load time). To adhere to this SLA, we did multiple activities, in code, process as well as infrastructure. These include (but not limit to) - Using best practices including (http://developer.yahoo.com/performance/rules.html) Determining the optimum number of calls to the databases, open connections, etc. Providing the fastest mechanisms to download associated content (such as stylesheets, JS files, etc. over CDN) And debugging the reason for the slowness of the websites, when ...

Theming in Whidbey using CSS

Continuing my blog titled Themes in Whidbey . I would like to mention some great points I did find out today about Whidbey featrures. How many times have you got sick of developing Sites which have themes???? I mean every page u create has to have, maybe in ASP, something like <link href="<%=Session["ThemeFile"]%>.css"/> I have been doing since a long time. Do mention if you have a simpler method of defining a variable CSS for your page!!! Whidbey simplifies this further. Now in ASP.NET, all you will have to do is Create Themes directory, if not aldready present, Create a directory for each theme required, maybe Black, Gray,etc. Dump your CSS files into this directory. in Page_PreInit method define the Theme as Page.Theme="<Theme directory Name>". Further can be made into Page.Theme=(string)Session["ThemeType"] and viola, your theme management is take care by ASP.NET When you want to change the theme, the...