Silicon Investor (SI) -- The First Internet Community

STOCKTALK

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 : Novell (NOVL) dirt cheap, good buy? -- Ignore unavailable to you. Want to Upgrade?

To: PJ Strifas who wrote (29841)	1/8/2000 12:06:00 PM
From: Scott C. Lemon	Read Replies (1) \| Respond to of 42771

Hello PJ, Somewhat off topic ... This is an interesting article and summary ... it shows that many assumptions can be made, and that stats can show almost anything they want to! ;-) Don't take this the wrong way ... I agree with the statements, in context, but I'm not sure that they have done a very good job of defining the situation, and the assumptions that people will make are very misleading ... > The study found that overall 60% of development managers plan to > delay writing apps for Windows 2000 until 2001 or later and that > 31.7% plan to "never" write Windows 2000 apps. In addition, > cross-tabulations focusing in on corporations currently running NT > show that 27% of those running NT on most of the client computers > in their company plan to "never" write Windows 2000 apps and 55% of > the NT users will not write Windows 2000 apps until 2001 or later. I read through all of the information and could not find a detailed explanation of exactly what a "Windows 2000 app" is! Can you give me your opinion? What is a Windows 2000 app? Did they strictly define this to the people that were being surveyed? From my perspective, I would think that a "Windows 2000 app" is one which is written to use APIs that are specific to Windows 2000 ... and one that would only run on Windows 2000 ... whether client or server. If my assumption is correct, then I too would say that it is crazy to write an application today that is specific to Windows 2000 ... but writing Windows applications, IMHO, will continue ... So the overall significance of this "report" is drastically diminished in my eyes ... yes, a smart development manager would not write Windows 2000 specific APIs and code into their applications ... but I'm not sure that really means a whole lot. ADSI (the Active Directory APIs) have been available for quite some time on non-Windows 2000 platforms (i.e. 95,98,NT) ... I'm really having a hard time trying to determine exactly what makes an application "Windows 2000" specific ... Scott C. Lemon