Skip to main content

Why not compile Java for Windows?

Since most Java applets run on PC platform, why not offer a compiled version of Java directly run in Windows without JVM? Users can still use standard Java via JVM, it's just a performance enhancement.
That would negate the entire purpose of the java development program. Notice how you asked the question, "...since most...!" That should indicate to you that not all OS's are windows platforms and the purpose of java is to provide a language that can be interpreted(or used) by all OS's. Just because a person can program doesn't mean they will be using a computer that will be of the Intel based family of mpu's. By doing what you suggest would restrict many programmers work to that platform, not to mention the compatibility of browsers and OS's to decypher the programmers intent. 

We can still use standard Java through JVM. Because some Java programs are just like windows applications without involving multiple platforms, a compiled version for windows doesn't hurt, it only provides users with one more choice. I'd like to know how much performance gain a compile version can offer, if someone could do a benchmark test. 

Actually, the reason why you don't see compilers for Java is that the language is not yet stable. By the time somebody creates a Java Windows compiler, a new version pops out of the hopper at Sun. It takes a lot of time and testing to get one done correctly, so it is just not yet economically profitable. You can find some compilers around, but if you look closely, you'll see they are mostly based upon one of the older JRE's. In one benchmark comparison at JavaOne, a presenter showed that compiled C++ code ran 6 times faster over Java 1.2 for the simple stuff. As more complex operations were invoked, C++ was running at many multiples faster. The JIT compilers have reduced some of the apparent slowness of Java when multiple passes through the same code are considered. If you really need the speed, you might consider writing your stuff in Java and then running a Java to C++ converter. It's a lot of steps to go through, though.
Labels:

Comments

Post a Comment

Popular posts from this blog

WebSphere MQ Interview Questions

What is MQ and what does it do? Ans. MQ stands for MESSAGE QUEUEING. WebSphere MQ allows application programs to use message queuing to participate in message-driven processing. Application programs can communicate across different platforms by using the appropriate message queuing software products. What is Message driven process? Ans . When messages arrive on a queue, they can automatically start an application using triggering. If necessary, the applications can be stopped when the message (or messages) have been processed. What are advantages of the MQ? Ans. 1. Integration. 2. Asynchrony 3. Assured Delivery 4. Scalability. How does it support the Integration? Ans. Because the MQ is independent of the Operating System you use i.e. it may be Windows, Solaris,AIX.It is independent of the protocol (i.e. TCP/IP, LU6.2, SNA, NetBIOS, UDP).It is not required that both the sender and receiver should be running on the same platform What is Asynchrony? Ans. With messag
11 comments
Continue Reading >>>>

Advantages & Disadvantages of Synchronous / Asynchronous Communications?

  Asynchronous Communication Advantages: Requests need not be targeted to specific server. Service need not be available when request is made. No blocking, so resources could be freed.  Could use connectionless protocol Disadvantages: Response times are unpredictable. Error handling usually more complex.  Usually requires connection-oriented protocol.  Harder to design apps Synchronous Communication Advantages: Easy to program Outcome is known immediately  Error recovery easier (usually)  Better real-time response (usually) Disadvantages: Service must be up and ready. Requestor blocks, held resources are “tied up”.  Usually requires connection-oriented protocol
Post a Comment
Continue Reading >>>>

XML Binding with JAXB 2.0 - Tutorial

Java Architecture for XML Binding (JAXB) is an API/framework that binds XML schema to Java representations. Java objects may then subsequently be used to marshal or unmarshal XML documents. Marshalling an XML document means creating an XML document from Java objects. Unmarshalling means creating creating a Java representation of an XML document (or, in effect, the reverse of marshaling). You retrieve the element and attribute values of the XML document from the Java representation. The JAXB 2.0 specification is implemented in JWSDP 2.0. JAXB 2.0 has some new features, which facilitate the marshalling and unmarshalling of an XML document. JAXB 2.0 also allows you to map a Java object to an XML document or an XML Schema. Some of the new features in JAXB 2.0 include: Smaller runtime libraries are required for JAXB 2.0, which require lesser runtime memory. Significantly, fewer Java classes are generated from a schema, compared to JAXB 1.0. For each top-level complexType, 2.0 generates a v
Post a Comment
Continue Reading >>>>