Tuesday, August 09, 2005

Code war heats up between Microsoft and Adobe

What happens when a smaller software maker enters a collision course with giant Microsoft Corp.? Adobe Systems Inc., a San Jose-based company with a large presence in Fremont, is poised to find out.

Redmond-based Microsoft just announced two products that will compete with offerings from Adobe, and Adobe is about to buy a company with products that challenge Microsoft's.
After that purchase, Adobe will practically own a rich market: software used by photographers, artists and Web developers to manage photos and graphic images and print them or create Web sites incorporating them.

Microsoft is active in just about every market except that one. And, as always, it's seeking ways to tweak its slowing revenue growth.

Microsoft says it's no threat. Some analysts don't believe that.
"For Microsoft to continue to grow at the rate it wants, it needs to be conquering new markets, and Adobe's is the biggest, juiciest prize right now," said Jesse James Garrett, a director at consultancy Adaptive Path.

The potential for a competitive clash began this spring.
In late April, Microsoft demonstrated software code-named Metro and now renamed the XML Paper Specification. It's digital-document software that in some respects competes with Adobe's market-dominating PDF format and its Acrobat family of products that produce or read that format.

Both companies' offerings allow creating documents that retain the quality of the included photographs, graphics and type and allow opening and reading the document dependably in multiple operating systems.

XML Paper Specification is planned as part Microsoft's Windows Vista operating system, released in beta form Wednesday.

Also part of Vista is the Windows Presentation Foundation, which incorporates Microsoft's XAML language for making documents and data automatically readable by multiple programs running on different operating systems.

That software could pose a competitive challenge to Flash, a well-established product from Macromedia Inc. Adobe in mid-April announced plans to spend $3.4 billion in stock to buy San Francisco-based Macromedia, in a deal set to close by this fall.

Vista plus XAML don't add up to Flash, exactly, but "they could obviate the need for Flash," said Gary Hein, an analyst with the Burton Group.

Macromedia also produces Dreamweaver, among the most popular products for building Web sites -- except for Microsoft's FrontPage and more sophisticated Visual Studio.
The fourth and final swerve toward a collision occurred last month, when Microsoft released Acrylic, the code name for a new, free graphics program.

The Acrylic Web site even echoes Adobe's distinctive packaging.

Early users say Acrylic includes some features of three Adobe programs designed for creative professionals: bit-mapped photo manager Photoshop and vector-based graphics managers Illustrator and Freehand.

Summing up these product developments, Hein observed: "It's almost like if you go down the list of products and abbreviations the companies are using, there's nearly a one-to-one mapping of what Adobe and Microsoft are providing."

At the moment, Adobe has a huge competitive advantage, holding between 75 percent and 90 percent of the market with each program it makes.

But that kind of lead alone doesn't ensure continued success, said Piper Jaffray analyst Gene Munster. What will determine when, or whether, Microsoft's software can equal Adobe's, he said, is simply this: "How hard does it want to go after the creative community?"

In the business-software segment, Microsoft is also poised to make inroads.
Whereas Adobe sells printer-makers the right to print documents using its Postscript type technology, Microsoft plans to give its equivalent technology away, Munster said. That gives it a better chance of edging into Adobe's market.

But two Microsoft executives maintain Adobe has nothing to fear from Redmond.
Conceiving of the two companies as being on a collision course is "a much more black-and-white way of looking at the world than exists in the space we're in," said John Montgomery, a director in Microsoft's developer division.

"Yes, there's competition -- and there's collaboration. Our relationship with Adobe has many layers. We all need to work together, because what we're all trying to do is advance the state of the art and make money by building better products."

And, he said, Acrylic isn't meant to compete with Adobe products.
"It's less a competitive product than a cooperative product," he said. "You'd probably use them (Acrylic and Photoshop) with each other."

Windows boss Jim Allchin in an earlier interview said Metro isn't intended to challenge Adobe's PDF format, though he acknowledged some will see it that way.
Adobe spokeswoman Katie Juran said no executives were available to comment.
Microsoft's reassurances don't carry much weight to those who remember how encounters with Microsoft have proved hazardous to smaller companies' health.

In the late 1990s, Netscape's once-dominant Navigator browser was savaged by Microsoft's Internet Explorer. Though Navigator still exists, its influence and market share are minuscule. Seattle's RealNetworks Inc. in 2003 sued Microsoft for antitrust violations over including Media Player within Windows. In federal filings, it says such inclusion has "substantially affected" its business.

How can Adobe stave off whatever competitive threat Microsoft might pose?
The company must reconcile itself to some market-share erosion from Microsoft, said Karen Haus, an analyst with WR Hambrecht + Co.

To increase Acrobat's appeal, Adobe could try bundling additional products with it and offering fixed prices over long periods in exchange for buying commitments, because corporate buyers tend to be price-sensitive, she said.

Adobe will have an easier time protecting its lead among creative professionals, she said. That's especially true if it bundles some of those products into "creative suites," as it already has with Photoshop, its Bridge browser and ImageReady, a Web preparation product.

Adobe has the additional advantages of an excellent reputation for quality and the Mac-oriented, anti-Microsoft bent of some in the artistic community, she said.
The biggest risk to Adobe would be getting diverted by the pending purchase of Macromedia, said analyst Garrett.

"I'd say the risk in a merger situation like this is avoiding confusion and disarray and the stagnation of product lines," he said. "Microsoft is not going to wait until Adobe is ready before it starts going after them."

To see more of the Seattle Post-Intelligencer, for online features, or to subscribe, go to http://seattlep-I.com.

Yahoo Introduces Upgraded Instant Messaging Service

Yahoo Inc has revealed that it has started to enable users to make telephone calls and surf the Internet through its "Yahoo Messenger with Voice" service, an upgrade of its instant messaging (IM) system.

The new service is said to enable high-quality voice calling, allowing users to make phone calls to family and friends anywhere in the world between PCs. According to Yahoo, IM is very popular amongst children aged 9-12 years old and teenagers and often accounts for the main part of their online time. The company is reported to have upgraded its IM service with the aim of drawing a young audience familiar with broadband web connections and with the intention of keeping rival voice-calling services at bay.

Yahoo is said to be attempting to fend off the increasing popularity of services such as Skype, an Internet phone calling service with around 48m registered users worldwide. Yahoo's service, to include free spam protection, photo-sharing and voicemail, is available at http://messenger.yahoo.com/ in 18 localised versions and is claimed to have attracted millions of users for the final testing.

Internet Explorer 7 User Agent String

Internet Explorer 7 Beta 1 is fast approaching. A tiny but significant code change was checked in this week: Internet Explorer's new User-Agent string.
The User-Agent (or UA) string is sent along in the headers of every HTTP request so the server knows what type of browser is making the request. For a quick introduction on handling of the User-Agent string, check out George Shephard's article in MSDN Magazine.

Internet Explorer 7 User-Agent

As we updated the User-Agent, we considered application-compatibility issues, historical precedent, and feedback from the community. We arrived at a very simple string.
IE7 running on Longhorn will send the following User-Agent header: Mozilla/4.0 (compatible; MSIE 7.0b; Windows NT 6.0)
There are three points of interest in this string:
  1. We updated from 6.0 to 7.0 to reflect the new application version.
  2. Consistent with prior betas, a "b" was added following the 7.0, in order to flag this as a beta release. This "b" will be removed for RTM.
  3. The "SV1" token was removed. As predicted by the community, this token becomes redundant with the release of IE7.

What does this mean for web developers?

If you use ASP.NET's HTTPBrowserCapabilities class on your pages, you'll find that it is already able to correctly interpret the new UA string. The class will return 7 for the MajorVersion property, and True for the Beta property.
Checks for the IE security features introduced in XP SP2 can be updated as follows:


System.Web.HttpBrowserCapabilities browser = Request.Browser;
bool isIESecurityEnhanced = (browser.Browser == "IE" && (browser.MajorVersion > 6 (browser.MajorVersion == 6 && Request.Headers["User-Agent"] != null && Request.Headers["User-Agent"].IndexOf("SV1")>-1)));


Can web developers test the new string out before IE7 Beta ships?
My first suggestion was to use a simple rule in Fiddler to change the outbound User-Agent header:


static function OnBeforeRequest(oSession:Fiddler.Session){ oSession.oRequest["User-Agent"] = "Mozilla/4.0 (compatible; MSIE 7.0b; Windows NT 6.0)";}
However, this will only report the new User-Agent to the web server; any script in the webpage that calls the navigator object to check the browser version will never notice this change. Rats.
Fortunately, IE5.0 and later allow you to override the user-agent string used by scripting and sent by the browser.
Simply save the following as IE7UA.REG. Double-click the file to merge it into your registry and restart the browser to see the change.


Windows Registry Editor Version 5.00