Scott:
>1. Do you think that Java will always be 'slow' and that Intel and
>others will not work to resolve this?
Not at all, with JIT compilers, and Java-on-a-chip, it will certainly get faster. Also as javabeans get incorporated, and enhancements made to the language it will get significantly faster.
For that matter, Moore's law will guarantee performance doubling a minimum of every 18 months.
>2. What kind of time are we talking? A year?
It will always get faster. If you are asking when it will be as fast and efficient as C, then never, unless a hardware solution is involved (assuming the programmer is good in both environments).
>Uh ... as an NLM developer, and a Java developer I have to disagree! >The Java tools are pretty bad these days ... and Java in no way >lends itself to the development of high-performance services. Not >today ...
Why don't you go to your friendly neighborhood computerstore, and look at all of the java toolkits, books, and software. Then go to the NLM section of that same store, if there is one...
Have you checked out the UNIX-native JDK's? Not just the ones that run on a PC?
>And the reason for a GUI on a service is? Why would I ever want to >burden a high-performance I/O service with a GUI? GUIs should be >developed independent of the service, and through a mechanism that >provides security, access control, and network transport >independence ... I would argue for a directory interface, unless >real time information is needed in which case SNMP is a better >standard solution ... both of which NetWare fully supports.
As others have said, JAVA is not just for I/O service routines. If NOVL keeps such an opinion on the proper place for JAVA, then it will be a mistake. Like it or not, if you look at some of the java classes and applet libraries on the web, you will have a difficult time finding non-GUI JAVA applications.
In order for Netware to be successful as an operating system, it must run (serve) application code. With a tight, fast JVM, it can. Would NT be as successful as it is today if it required WLMs? (Windows Loadable Modules)
>From my basic mathematics I remember that large numbers of people >tend to cluster around the center of the bell curve ... that's >average! The people who push the limits will end up at one end or >the other. At my last couple of start-ups, we actually made a lot of >money, quite easily, just because not many people have the expertise >and the skill to right NLMs.
That's my point. The world isn't breaking down your doors to write NLMs. If that was the case you would see NLM sections of computer bookstores instead of JAVA sections. Your companies got a premium because there were relatively few people out there with the skillset to write NLMs.
>A Windows app? Easy ... I can write crap code and if it blows up, the user will just re-boot ... they're all trained by Microsoft! ;-)
Agreed -- It seems that MSFT has cornered the world in crappy programmers :) |
