To: Mary Cluney who wrote (61889 ) 8/7/1998 12:50:00 AM From: Mike Wong Read Replies (2) | Respond to of 186894
I have been a software developer for years, and one things that seems to be the holy grail is a language that runs on everything. Ten years ago it was "C", now its JAVA. Management types all love the ticky marks on a chart that says that their application runs on everything. Ome thing they always do not talk about is performance. Hardware always takes care of that problem, so they say. However, 1. JAVA is not platform independent if the programmer writes platform dependent code, regardless of what language he uses. As a matter of fact, SUN has a bunch of WEB pages that shows how that should be done. 2. I have read that JAVA is anywhere from 3X to 500X slower than "C" depemding on what you are trying to do, and depending on who makes the interpreter. As a matter of fact, I read that many companies that started writing in JAVA (eg Corel), stopped using it, once they found out how slow it was. In addition, there is less functionality than existing languages, not because of any inherent limitation, but because it is less mature. So a program written in JAVA will have less functionality than one written in traditional "C". By the time JAVA moves ahead in functionality, "C", and "C++" will have moved ahead that much more. 3. JAVA is supposed to make software run not only on Intel platforms, but other hardware platforms as well. So I have to take a big degradation in performance to run on a SUN and PowerPC platforms. Hmmm..... What if I am perfectly happy with my Intel platform? 4. JAVA will only run on some given platform if somebody writes an interpreter for it on that platform. So if you have a chip that can run a car engine, you'll need to invest bookoo bucks to get a JAVA interpreter for it before you can program it. IBM and SUN aren't writing any interpreters for them. So it seems a lot faster to write in native assembler or "C". 5. SUN is claiming that Microsoft is deliberately making their JAVA different from the JAVA standard. The key word is "deliberate". Software is so complex that you dont have to be deliberate to have different versions be incompatible. That said, let me get off the technical issues. In software, it is still hype that causes momentum, and momentum solves all technical issues. Once people write many programs with some tool, demand will happen for more tools to solve problems this tool may have. So whether JAVA will succeed or not is dependent less on what technical merits it has, than the hype it generates. McNealy is pretty good at salesmanship. So far, I think the jury is still out whether it will succeed or not.