To: carolyn walder who wrote (2818 ) 3/1/1998 11:21:00 PM From: Jason Cogan Respond to of 10309
Carolyn: Your analysis of WIND's core business and need for a hard RTOS is right on. As you indicated, I believe the recent licensing of Navio technology was done as a means of challenging Microsoft and others in the set-top space, rather than the other way around. The core needs for a hard RTOS are inumerable, but certainly include military, routing (telecom), and i2O (embedded routing). For Mark and other doubters, keep in mind that Microsoft does not currently have a hard RTOS, and from the conference call, WIND management does not regard CE as ready for that space. In addition, Microsoft has some other obvious disadvantages to WIND, many of which I indicated on an earlier post. Among them: 1. Lack of a complete tool kit, such as Tornado, that makes development of applications easy and standardized. What's more, Tornado is the industry leading standard for third-party tools and other functionality not captured under the existing framework. 2. Increasing installed base of users familiar with Tornado. 3. Widest number of processors supported, which is key to the embedded systems space. No two applications are exactly alike, and thus require a multitude of different processors. 4. Wind is not Microsoft. This presents a tremendous advantage to many of the potential customers, such as Sun, who would rather deal with ANYONE than cede the embedded space to Microsoft. Of course, there are many other manifestations of WIND's market leadership in this area. The biggest drawback to growth continues to be the insistence on "roll your own" applications in certain sectors, such as in the automotive and wireless industries. But as time to market demands constantly increase, the needs to standardize around a common tool kit become all the more powerful. Ask yourself. You could program your own operating system on a PC, rather than buy one from Microsoft. But how efficient is that? The same logic should be even more powerful in the embedded space. Regards, Jason Cogan