Re: Java and NC

Mike Segel <mikey@segel.NOSPAM-.KING.OF.MYDOMAIN.-NOSPAM.com> wrote: >Actually, NC's are better for intranet apps than PCs. >Look at the cost of maintanence of a PC versus an NC. >By stripping down the PC, you lose configuration problems. >You lose the hassles of some user modifying his/her OS from 3.11 >to '95 then demanding support. The advantages of NC are well known. But do you see corporates who have spent millions on PCs dumping them all in favour of NCs? Most of them here won't. >You control software apps from a single point of distribution. Bur this only because you have thin clients. Java allows you to build thin clients for both NCs and PCs. You can't use this argument in favour of the NC. The thin PC version can also be loaded off the network. >VJ++ ? Let me get this straight. You want to take a portable >language, Java, and add Machine dependant code which makes your >application less portable? No. It is still 100% Java. There is no machine dependant code in it. The choice you have is that you can produce JVM p-code or Windows EXEs and they will run happily on both environments. At the moment. the exe version executes about 10 times faster than the jvm version. >Hello? Am I the only one who thinks that this is strange? I wouldn't go as far as to say it is strange. I would say it is unfortunate. >The biggest feature of Java is that it is machine independant. >This way, when I write an app, it will run on any machine. Which means >I can then buy the hardware best suited to my needs. I disagree. The biggest feature of Java is that it allows you to produce thin applications. But if an organisation has lots of PCs, there are lots of advantages in producing an exe version for them to use. When you get NCs, you can then compile a jvm version as well. David David W Chan GO5 Limited david@go5.com (work) dwc@cix.compulink.co.uk (home)