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 : Novell (NOVL) dirt cheap, good buy?

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: E_K_S who wrote (10428)3/29/1997 9:08:00 PM
From: BP Ritchie   of 42771
 
We might be missing something important here ... 'Mystery man explains ... '

I think there are significant differences between NT and NW. NW has been built to work as a Server from the beginning, because of this 'design objective' it has much better performance than NT and much better (Reliability, Availability, and Servicability) RAS than NT. NW is not a 'general purpose OS' ... it is a Server OS.

Even NT is not really a 'general purpose OS' ... OS/2 probably comes closer to that description than any Windows product to date. All Windows products are first and foremost ... a USER INTERFACE, then a PERSONAL Computer OS ... ie the design objective is concerned with ONE user. The reason that MSFT is trying to differentiate NT Server from NT WS is that they do understand that 2 different design points are required and MSFT will not be able to provide a decent Server before NT 5.0 (IMO ... probably not on the NT 5.0 ship date either).

There is a major move of applications runtime requirements underway, away from a ONE user PC application into a 'Network application' ... JAVA is a 'network application' language, CORBA & ORBs are PUBLIC Network ideas ... DCOM is a MSFT Proprietary Network idea. A 'Java virtual machine' is really an application execution environment that 'emulates' on the host OS & Hardware all of the Java support that the application requires ... it is reasonable to expect a JVM on IntraNetware to be implemented as an NLM.

Sun & Novell are providing Application Development Tools that allow programmers to build Java applications that can be targeted to run on any JVM ... with Development time 'hooks' that support interactive development and debugging on IntraNetware and Solaris ... this was a very important 'missing piece' for Novell until this week. Now the development facilities that MSFT had for NT (targeting DCOM, etc) will no longer be capable of shutting out IntraNetware as a runtime target. This is how the two 'Servers ... NT & NW' are becoming more 'alike' ... to developers.

What should not be overlooked is the remaining very substantial difference in design objectives ... NW is still very much superior to NT in performance and RAS ... a JVM on NT will only widen the difference. NW still beats NT by a wide margin ... and the margin gets wider with every PC application that migrates to a Network application. What just happened is essentially a reduction in MSFT's ability to use Application Development Tools like a 'Roach Motel' to force developers to target NT for runtime and to exclude NW.


Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext