SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : Wind River going up, up, up!

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: Allen Benn who wrote (664)3/12/1997 11:25:00 PM
From: Michael Greene   of 10309
 
>>While Microsoft has the theoretical potential to be a serious competitor in the RTOS space, they still have not made significant overt moves that are particularly threatening. Their trump card, the Win32 API, has been finessed by the Willows RT announcement. To the extent that the Win32 API is popular or that Win32 API legacy code exists, it can be accommodated within VxWorks via Willows.

When I first saw the Willows RT announcement I thought that this was a major coup for WIND and would prove to be very attractive to embedded developers. Recently, I saw another article embedded.com which casts some doubt in my mind. This article states "the Willows solution requires recompilation and linking with the TWIN libraries. Thus, only the software for which you have the source code is executable with the exception of 16-bit DLLs, for which an emulator is available."

Rather than build everything from scratch don't windows developers typically make use of available libraries of windows components, much of it supplied in object form rather than as source code? If this is true then the Willows solution appeal would be greatly diminished since these major productivity aids would no longer be available. Anyone familar with this issue please comment.
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext