Philip Brittan's Blog

Java vs. .NET, part 2 - The Nature of the Beast

What is Microsoft trying to do?

Microsoft is the uncontested champion of the desktop. In the business world, they own essentially the entire client-side market. This is a huge advantage for them. But it is also a limitation. In order to fuel its growth, Microsoft must find new, less-tapped-out markets to go after. The server room is one such market. Microsoft is already strong there, but they still have a lot of share to grow into, and it is a lucrative market.

In my previous post in this series, I claimed that Microsoft has the upper hand when it comes to the quality of the user experience. Microsoft�s user experience leadership is completely bound up with their domination of the desktop. It makes sense for Microsoft to use their hegemony on the desktop to their advantage. The client PC is their solid base, and .NET is the lever to get back to the target. .NET is an expansive strategy with many interlocking parts, and these parts come into play at various stages in Microsoft�s siege of the server room.

The UI layer of .NET is the tip of Microsoft�s spear. Microsoft leverages its usability advantage, combined with its very strong tools offering, to convince developers to adopt .NET as their platform for application development and deployment. .NET apps are delivered either as ASP.NET Web pages or as managed CLR fat clients. The thing is, in order to deploy and power .NET apps on the client or in the browser, you really need to install Windows servers, preferably Windows Server 2003 (formerly known as Windows .NET Server), in the server room. Ideally, you�ll also finally upgrade to XP on the desktops to boot!

From there, Microsoft uses the expansiveness of the .NET strategy to push out Oracle in favor of SQL Server and gets companies to install BizTalk and other Microsoft server technologies. The fact that so many companies already rely on Exchange for email helps in this. Microsoft will demonstrate the power and ease of using a pre-integrated stack from a single vendor to get customers to adopt more and more of their technology.

This is the threat that non-Microsoft vendors and the whole Java community faces. This plan is ambitious, but it is by no means easy, even for a company with the resources and advantages of Microsoft. Its success hinges largely on Microsoft�s ability to convince developers to adopt .NET. Therefore, the Java community�s challenge is to keep the tip of Microsoft�s spear from getting in by convincing developers and sys admins (and the companies that employ them) that Java has a more compelling answer for applications delivery than .NET.

(to be continued)

Comments

• Microsoft's "new" challenger for supremacy
  With Novell buying Ximian, Linux has a VERY credible sponsor for its competion with Microsoft. Ximian is the lead organisation in the GNOME developement and in Mono , the other .NET implementation, the one done to standards.

  Novell's directory is superior to Microsoft's directory. Gnome is a good contender for the Windows UI. Both run on top of Linux, an operating system where development leads more quickly to implementations relative to what Microsoft does, Novell can concentrate on services that add value.

  Microsoft is handicapped as it want to do it all alone. Novell will get additional markets as people decide to go in a direction as they can piggy back.

  Microsoft has achieved a lot but their TCO runs foul on one basic fact; I do not have that cash to buy into their dream. So as the restrictive practices become ever more repugnant the installed base reduces and the power to move is reduced. I am gratefull that competion is not dead.
  Thanks,
  Gerard

  Posted by: gerardm on August 07, 2003 at 07:48 AM

• Keeping w/ the winning MS tradition
  The reason that Microsoft has been so successful is that they provide a huge base set of functionality that all companies can count on. It is such a large incentive. You know what are all the APIs that you can count on, and simply publish that your product works on MS Win2K or XP or .... If Microsoft only installed some stuff, then there would be lots of confusion and everyone would need to bundle their own versions of the non-core components.

  I believe what Sun and Java do is enable a similar playing field for Java developers. As long as the target platform is JDK 1.4 or above, my application will run. I don't need to worry that some little used API wasn't part of the default install, and because I can't distribute it, I will not need to bundle my own, in case there are problems with the behind-the-scenes download you speak of.

  People are looking for guarantees, otherwise, they will leave the platform. This is one thing that MS has done well that I believe needs to be followed.

  Posted by: rgupta1 on August 07, 2003 at 06:20 PM

• You will need Windows servers?
  Dear Philip,

  you wrote: "in order to deploy and power .NET apps on the client or in the browser, you really need to install Windows servers, preferably Windows Server 2003 (formerly known as Windows .NET Server), in the server room"

  It gives me the shivers if .net users actually will be compelled to do so. Wouldn't that unmask all the announcements of microsoft regarding .net being some kind of "open standard" and able to interact with the rest of the world as being just the usual sort of marketing perversions? And .net would turn out to be just another attempt to conquer the lucrative server market...

  However, is that really true? Even when one happens to be a little Microsoft sceptic, it's hard to believe that they were such fools of putting their sleeve on another "closed water system" in times of growing interability needs.
  Or did I take something amiss with .net all the time?

  Regards,
  Matthias Paul Scholz

  Posted by: mpscholz on August 07, 2003 at 11:29 PM

• You will need Windows servers?
  Matthias Paul Scholz :

  Get with the program. In order to run asp.net applications, you need IIS. IIS only runs on Windows Servers. One more thing is that asp.net doesn't run on Windows NT. If your organization uses Windows NT, you either need to upgrade or you're out of luck.

  There are open source efforts underway to port C# and 'parts' of the .net framework to linux and other platforms, but we're years from that reality. These efforts don't make Microsoft's strategy any kind of 'open standard.' Microsoft will never endorse such efforts. Their aim is to force you to upgrade (if you're running Windows NT) or 'lock' you into windows servers.

  Posted by: jpatel on August 08, 2003 at 03:47 AM

• .NET
  As I understand it, the only 'standard' of .net is the C# programming language.
  That said the article does layout exactly what Microsoft wish to do.

  Unfortunately I don't believe that Java can offer the answer (alone) the article points out that MS strength lies in it's offering everything, with an easy (ish) interface.

  The only way to combat the market leaders is to be better (not just as good). So a combined platform of nice GUI (gnome) and GUI tools for setting up apache (a standard IIS style tool) and integrated J2EE.

  Our company has gone with microsoft (.net)because we can take any bright person, sit them in front of w2000 and IIS and they can configure an SSL ASP webserver pretty quick. without requring a phd in command line, modules,and compiling apache etc.

  I'm hoping SUN can contribute more (java) tools to GNOME to make it a working GUI. But who knows with Novell now taking ximian, which was decent.

  [i apologise for the linux, but .net is a platform rather than a development environment]
  

  Posted by: blazeya5 on August 08, 2003 at 06:48 AM

• You will need Windows servers?
  If a vb programmer needs ASP on a Unix host running Apache, she can use chillisoft. If a java coder needs JSP on IIS he can use the redirect ISAPI filter.

  Given that asp/jsp are just a means to tie your dcom/remoting/com+/ejb/javabeans logic to xml/html/css/dom, this oil and water comparision is a little over emphasized.

  The beauty of java on the server side is that it doesn't care if you're running a win server or a linux box. So policy and individual tastes will drive this mix-and-match environment.

  The low cost and high quality of JBoss, Tomcat and the like, means more people will try this mixed environment, and the infrastructure will continue to commoditize.

  Then the next question is, when it's time to upgrade servers, do you invest in licenses, or opt for reduced-cost, high quality solutions like BSD/Linux, and channel the savings into expert services, like JBoss Group, or training, or value-added productivity tools?

  And if you choose licenses, does that preclude you from installing that jvm and application server?

  In addition, the ui hold is a misdiagnosis. As more developers experiment with ASP.net they begin to realize something: the flashy and complex gadgetry hides simple w3c web standards like css, xml, dom and the like.

  The next realization is that to work with those simple primitives, they have to 'undo' layers of complexity, until they realize it's much easier to write it themselves in the first place.

  [in regard to WinForms, as the original author's loaded diction implies, 'fat' clients are passe' ;)]

  Posted by: d_bleyl on August 08, 2003 at 07:34 AM

• Microsofts Server Room Barriers
  |
  |One of the barriers to entry that Microsoft has faced in the server room
  |is the skill set of the systems administrators
  |

  No it hasnt.
  Quite the opposite in fact (most Microsoft shops dont have the unix skills for Linux)

  The main barrier Microsoft has faces has been either the perception or the reality that:
  1) Windows Servers dont scale
  2) They are not reliable.
  3) They are not secure
  4) They are popular virus targets
  5) They are expensive to maintain

  -Nick

  Posted by: nickminutello on August 09, 2003 at 07:04 PM

• Microsofts Server Room Barriers
  Nick -

  Thanks for your comments. I agree fully with the barriers that you list. And Microsoft has been putting on a full-court-press top overcome these perceptions (and perhaps the realities) in the marketplace.

  By "quite the opposite", I assume you mean the 'converse': Linux has been having a hard time getting a foothold in Microsoft shops because of a lack of administrator skills. That may well be the case.

  Clearly, my original comments were not about Microsoft shops but were rather describing Unix/Linux ones.

  Best,
  - Philip

  Posted by: pbrittan on August 11, 2003 at 01:39 PM

• Microsoft says .Net usage passes Java
  I'm sure you've all seen this:

  http://www.infoworld.com/article/03/08/07/HNMicrorudder_1.html
  

  Posted by: pbrittan on August 11, 2003 at 05:45 PM

• You will need Windows servers?
  Fat clients have been passe', but Microsoft is determined to bring them back.

  Yes, ASP.NET is an important part of .NET, but I actually do not think that Microsoft is interested in promoting browser-based DHTML clients. Strategically, they need to continue to lock in Windows on the desktop, and fat clients are the strongest way to do that.

  I believe that Microsoft's main strategic thrust will be around "Smart Clients". Smart Clients are .NET fat clients that rely on Web Services (served up by Windows Servers) and that can be trickeled to the client machine byte-by-byte, to make installation much more seamless to the end user. But they are still locally-installed Win32 applications.

  Usability will be a primary driver for Microsoft to promote Smart Clients. Usability doesn't just mean the quality of the GUI or the richness of the controls (although those are very important). It also includes the ability to interact with other applications on the desktop (a big problem for browser-based apps) to provide an overall superior user experience (anyone remember the "Are you experienced?" campaign?).

  Here is an excerpt from a newsletter that Microsoft sent around to ISVs this morning:

  "ISVs: Get Ready to Deliver Smart Client Applications
  The Smart Client Readiness Program for ISVs gives you the software, tools, and technical resources you need to start building smart client applications. If your customers aren't asking for them yet, they will soon see the need for the next generation of anywhere, anytime data access. Enroll in the program today!
  http://go.microsoft.com/?linkid=215945"
  

  Posted by: pbrittan on August 12, 2003 at 06:35 AM

• Indigo

  Indigo is expected to reach developers at about the same time as the launch of the Longhorn edition of Windows Server, according to a recent presentation given by Microsoft's senior vice president for servers and tools, Eric Rudder.

  A software company executive familiar with Indigo identified one potential trouble spot. The software could diverge from industrywide Web services standards in order to optimize applications to run on Windows, he speculated. That would run counter to the idea of Web services as an open industry standard.

  "Microsoft is saying, 'All this open standards with Web services has gone far enough,'" said the executive, who requested anonymity. "It's back to the movie as we know it."

  Microsoft representatives declined to provide additional details about Indigo.

  Read the full story on News.com
  

  Posted by: pbrittan on August 13, 2003 at 02:04 PM

• Ah ha - they have a strategy.
  Thanks for the insight - I haven't heard of Smart Clients until now. Your analysis makes a lot of sense, especially if they plan to leverage the Office System as a building block.

  What is the java analog to Smart Clients?

  Posted by: d_bleyl on August 14, 2003 at 01:47 PM

• New MS Office locks down documents
  I just put a relevant comment in another blog

  Essentially, MS is going to use the Rights Management features of its upcoming Office 2003 suite to lock out competitors and drive Windows SErver sales.

  Posted by: pbrittan on September 02, 2003 at 06:32 AM

• .NET
  "without requring a phd in command line, modules,and compiling apache etc"

  I just don't understand what you're talking about. I built a webserver from scratch, installed Linux, installed Apache, am running 4 websites on it. I didn't have to compile anything and haven't any formal qualification in computer science. The only "skill" required was being able to read.

  Posted by: observer386 on September 08, 2003 at 12:38 AM

• Ah ha - they have a strategy.
  Java does have an equivalent called "Java Web Start" which can be used with JRE1.3 and comes with JRE1.4. Web Start can use Swing, AWT, or SWT for building these kinds of applications. Check out the samples that come with Web Start to get an idea of how it can work.

  Posted by: panurge on October 01, 2003 at 11:42 AM

• 网络营销软件
  网络营销软件
  网络营销软件
  群发软件
  群发软件
  ---
  群发软件
  网络营销软件
  论坛群发软件
  网站排名软件
  群发软件
  推广小助手破解版
  论坛群发软件
  网站排名软件
  群发软件
  推荐给你很好的群发软件和信息群发软件和供求群发软件
  推荐给你很好的群发软件和信息群发软件和供求群发软件博客群发软件网络营销软件网络营销软件
  网站排名软件网站排名软件网站优化软件信息群发软件信息群发软件信息群发软件论坛群发软件网站推广软件网站推广软件博客群发软件博客群发软件

  群发软件群发软件博客群发软件论坛群发软件网络营销软件论坛群发软件
  信息群发软件推广软件网站推广软件网络营销软件网站推广软件群发软件网站排名软件网站推广软件博客群发软件论坛群发软件群发软件网站排名软件网站推广软件博客群发软件论坛群发软件
  网站排名软件
  博客群发软件
  网站排名软件
  网站推广软件
  群发软件信息群发软件
  免费论坛群发软件
  论坛群发软件
  网站排名软件
  免费博客群发软件
  网站推广软件

  群发软件
  博客群发软件
  网站排名软件
  网站推广软件
  群发软件信息群发软件
  免费论坛群发软件
  论坛群发软件
  网站排名软件
  免费博客群发软件
  博客群发软件
  信息群发软件
  论坛群发软件
  信息群发软件
  博客群发软件
  qq群发软件
  邮件群发软件
  博客群建软件
  企业名录搜索软件
  信息群发软件
  邮件群发软件
  论坛群发软件
  博客群发软件
  网站推广软件
  网络营销软件
  全能营销破解版
  网络营销软件
  论坛群发软件
  论坛群发软件
  论坛群发软件
  网络营销软件
  信息群发软件
  信息群发软件
  信息群发软件
  群发软件
  

  Posted by: mimi9989 on December 06, 2007 at 06:26 AM

• wow power leveling
  wow powerleveling
  wow power leveling
  wow gold
  wow items
  feelingame.com
  wow tips
  Most Valuable WOW Power Leveling Service
  wow power leveling faq
  cheap wow power leveling
  wow power leveling
  wow powerleveling
  wow power lvl

  Posted by: wowleveling on December 13, 2007 at 01:09 AM

This work is licensed under a Creative Commons License.