Browser Wars Redux

The entry of Google Chrome into the market initiates a new phase in the web browser wars. This phase might present some challenges to SQL Server developers, who could wind up needing to use JavaScript instead of ASP.NET to create front-end applications.

Google’s recent beta release of the Chrome browser has reignited the fight for control of the web. It’s no secret that Microsoft has owned the browser space ever since it vanquished Netscape several years ago by bundling Internet Explorer (IE) with the Windows OS. The emergence of the Mozilla Firefox browser never really threatened Microsoft. Although Firefox has gained about 20 percent global market share, it’s never mounted a serious bid to overtake IE. However, the continued success of Firefox underscores the dissatisfaction that businesses and end users have with IE, and perhaps with Microsoft in general.

Why Is Google in the Browser Business?

Google is a far cry from little, unthreatening, open-source Mozilla. Google’s release of Chrome is nothing short of a shot across Microsoft’s bow. Microsoft sees Google as its primary competitor: Google’s web-only orientation threatens to undermine Microsoft’s desktop dominance by supplanting the use of standalone software with web-based tools and services. Although we’re not quite there yet, it’s clear that cloud computing and Software as a Service (SaaS) are powerful emerging trends in the tech industry. The web browser enables SaaS (or Software Plus Services—S+S— if you feel particularly Microsoft-inclined) and cloud computing.

Although I didn’t expect it, I can see why Google wanted to develop a browser of its own. Google’s offerings are exclusively web-based and most users get to them via Microsoft’s IE. This leaves control of Google’s key web access technology in the hands of its biggest competitor. By creating Chrome, Google attempts to wrest control of this critical link from Microsoft and remove its dependence on its rival’s browser. Microsoft will certainly want to maintain its market position on the web and on the desktop. The software giant will continue to promote software-oriented solutions. This could deter Microsoft from whole-heartedly supporting future web technologies that might threaten its core business lines.

Does Chrome have a shot at the title? If the continued success of Firefox is any indication, I think it does. At first, to even know about Firefox you had to be a bit tech savvy—even finding it was a challenge. Not so with Chrome. Everyone who uses Google (and isn’t that everyone?) will be exposed to Chrome. Chrome is sure to have a major impact on IE and Firefox users.

Chrome’s Impact on SQL Server Development

Although SQL Server isn’t at the forefront of this epic battle, there’s no doubt that SQL Server developers will be affected by the new Chrome browser. Today, the majority of SQL Server applications are created with ASP and ASP.NET. The emergence of Chrome, with its revved up V8 JavaScript engine, has the potential to reshape the face of web applications. It could affect the future of web development technologies that will need to access SQL Server’s database services on the backend.

Who Wins?

In the long run, Google’s entry into the browser market is a win-win situation. Microsoft’s development of IE stagnated until Firefox emerged. Firefox spurred sleeping Microsoft into action, which resulted in a new and improved IE that incorporated the best features of Firefox. At the very least, Chrome’s arrival on the scene will encourage Microsoft to protect its market position by making improvements in IE. This competition is good news for users: No matter which browser you choose you’ll be using a better product. Beyond that, Chrome might be a key step forward in the evolution of cloud computing. May the best browser win!

Discuss this Article 1

Rich (not verified)

on Nov 27, 2008

This article, in general reflects many similar statements of one of my co-workers a few months previously. Pre-Chrome comments, but with cloud computing and open source programming in mind. The interesting thing is that my co-worker and friend is very technically inclined, and our company utilizes PC's and Windows, and Microsoft software for the most part, but two of my co-workers in our CRM Admin department both own, use, and prefer Mac's at home, which seems very much of interest to me, because they are both quite knowledgable and capable in working with databases and business logic. Also of interest, is that our company, as so many others uses a combination of Oracle and Siebel. I very much appreciate the advances and interface in SQL Server 2008, but M.S. should continue growing trend in becoming more sensitized to their customers and the importance of 'user-friendliness', which I'm not sure is totally employed, for instance in the most recent version of M.S. Office. Powerful, yes, but, for example, it takes longer for me to do several things in Excel (above and beyond the 'learning curve') than in previous versions. For instance, how about allowing more ability with the keyboard, and stop assuming that using the mouse is always a preferred thing for the user? At work, I need to go fast, very fast, and I don't have time to move my hand from my keyboard to my mouse all the time. Thnink about it, although often of value graphically, it's an extra move of the body, of time, and expenditure of energy. But there I go, a whole different rant (but not rave). Even so, it is within the scope of this article, in general. The moment that some companies settle into their throne and install some padding of their own, if they get too comfortable and hard of hearing with their subjects, someone else comes in to replace their Enterprise. One question that comes to my mind is, Tunnel vision? Will my patronage to Microsoft limit my future marketability?

From the Blogs

My initial goal in writing this series of posts was to outline some of the concerns surrounding Availability Groups (AGs) and SQL Server Agent Jobs – and call out how there is virtually no guidance from Microsoft on this front and then detail some of the pitfalls and options available for tackling this problem domain. I initially expected this series of posts to have between 25 and 30 posts – according to some of the early outlines I created ‘way back when’....More

Throughout this series of posts I’ve taken a somewhat pessimistic view of how SQL Server Agent jobs are managed within most organizations – meaning that most of the code and examples I’ve provided up until this point were based on assumptions about how CHANGE to jobs is managed. That pessimism, to date, has come in two forms:...More

In this series of posts I’ve called out some of the concerns related to SQL Server AlwaysOn Availability Groups and their interaction with SQL Server Agent jobs – both in the form of Batch Jobs (see post #3) and backups....More