Skip to main content

JRE vs. JDK

 

The JRE and the JDK are two terms you hear people mention very frequently in the Java world, and what they are the two parts that we need in order to run and create Java applications. The JRE is the Java Runtime Environment. JDK is the Java Development Kit. And so, the JRE is what you require in order to run Java applications, and end users normally install the JRE. They're the ones who are going to run our apps. The JDK provides the tools that we need to create Java apps. So, normally, developers are the ones who install the JDK on their machines. And in order to develop apps, you need to run them, so the JDK installation includes a JRE. So how does all this work together? If we sit down, and we type up a Java source file with our program code inside of it, and we want to go ahead and run that in some host environment, how do we do it? A host environment might be Windows, Linux. It could be Mac. It could even be a browser. It might be a phone running Android. How do we get from that source code we've typed up to something that can run on that other computer? Well, that's where the Java Development Kit comes in. Using the Java Development Kit, we can feed our source code into it, and it will produce our Java application. Now Java's does not like a low‑level language like C. C, when you compile a C program, it produces an application that can run directly on the host computer. Java uses an abstraction called byte codes that's platform independent. It allows us to not be tied to a host environment, but we have something that can be run in different host environments. And that's where the Java Runtime Environment comes in. The Java Runtime Environment provides what we need for our Java app to display codes that execute in any host environment. So that's why end users install the Java Runtime Environment because they just need to run that code. We, as developers, install the JDK to give us the tools to produce that application.

Comments

Post a Comment

We appreciate your valuable Suggestions/Feedback

Popular posts from this blog

Variables, Data Types and Math Operations

  In order to do anything interesting in a program, we must have the ability to store and manipulate values. What allows us to do that are what we call variables. Now a variable, simply put, is just named data storage. Now Java is a strongly ‑ typed language. Now what that means is that when we declare a variable like, in this case, we have a variable named data Value, we have to specify the type of that variable, in this case, it's what we call an int, something that can store integers. So, what that means is that the data Value variable can only store things that are compatible with the type int. As we go through the course, we'll talk about this idea of one type being compatible with another. Now when we declare a variable, we can, of course, then assign a value to it, so our variable data Value now holds the value 100. Now when we use variables, we can do it the way we've done here where we declare it, then assign it, or as a matter of convenience, we can declare them a...
Post a Comment
Read more

Publish a Project

Publish a Project: Publishing means packaging/archiving the project. Why to Publish : Robot can execute only Packages, doesn’t run projects directly. So we need to archive all project files to a Single Package file. There are 2 Process are available 1.        If Orchestrator is connected through Robot, automatically Project archive file displayed in Packages folder. From here, we can distribute this to some other Robots 2.        If there is no connection between Orchestrator and Robot, we need place Project archive file in Packages folder manually How to Publish: 1.        Open UI Studio, Create New Project 2.        In the Setup ribbon tab, click Publish . If the project is published successfully, the Info dialog box is displayed and the project is copied to the NuGet location set in the NuGetServerUrl parameter, in the UiPath.settings...
Post a Comment
Read more

AGILE Methodology

Agile:      Ø   Agile is nothing but a Multi Iterative Cycle      Ø   It breaks the entire project into Small pieces and then do implementation iteration by iteration      Ø   At the end of every Iteration, customer uses application and gives feedback      Ø   At the end of ALL Iterations, customer will get the application as desired Various versions of Agile: Scrum:                     In Scrum, each iteration is called ‘Sprint’. So, at the end of Sprint, Customer interacts with application and provides feedback (Unlike Waterfall) 3 Roles:   Ø   Product Owner   Ø   Scrum Master       Ø    Team
Post a Comment
Read more