Chapter 1

Welcome to Java

IN THIS CHAPTER

check Finding out about programming

check Scoping out Java

check Comparing Java with other programming languages

check Understanding Java’s incomprehensible version numbers

This chapter is a gentle introduction to the world of Java. In the next few pages, you find out what Java is, where it came from, and where it’s going. You also discover some of the unique strengths of Java, as well as some of its weaknesses. Also, you see how Java compares with other popular programming languages such as C, C++, and C#.

By the way, I assume in this chapter that you have at least enough background to know what computer programming is all about. That doesn’t mean that I assume you’re an expert or professional programmer. It just means that I don’t take the time to explain such basics as what a computer program is, what a programming language is, and so on. If you have absolutely no programming experience, I suggest that you pick up a copy of Java For Dummies, 7th Edition, or Beginning Programming with Java For Dummies, 5th Edition, both by Barry Burd (Wiley).

Throughout this chapter, you find little snippets of Java program code, plus a few snippets of code written in other languages, including C, C++, and Basic. If you don’t have a clue what this code means or does, don’t panic. I just want to give you a feel for what Java programming looks like and how it compares with programming in other languages.

Tip All the code listings used in this book are available for download at www.dummies.com/go/javaaiofd6e.

What Is Java, and Why Is It So Great?

Java is a programming language in the tradition of C and C++. As a result, if you have any experience with C or C++, you’ll often find yourself in familiar territory as you discover the various features of Java. (For more information about the similarities and differences between Java and C or C++, see the section “Java versus Other Languages,” later in this chapter.)

Java differs from other programming languages in a couple of significant ways, however. I point out the most important differences in the following sections.

Platform independence

One of the main reasons Java is so popular is its platform independence, which simply means that Java programs can be run on many types of computers.

Before Java, other programming languages promised platform independence by providing compatible compilers for different platforms. (A compiler is the program that translates programs written in a programming language into a form that can actually run on a computer.) The idea was that you could compile different versions of the programs for each platform. Unfortunately, this idea never really worked. The compilers were never identical on each platform; each had its own little nuances. As a result, you had to maintain a different version of your program for each platform you wanted to support.

Java’s platform independence isn’t based on providing compatible compilers for different platforms. Instead, Java is based on the concept of a virtual machine called the Java Virtual Machine (JVM). Think of the JVM as a hypothetical computer platform — a design for a computer that doesn’t exist as actual hardware. Instead, the JVM simulates the operation of a hypothetical computer that is designed to run Java programs.

The Java compiler doesn’t translate Java into the machine language of the computer that the program is running on. Instead, the compiler translates Java into the machine language of the JVM, which is called bytecode. Then the JVM runs the bytecode in the JVM.

When you compile a Java program, the runtime environment that simulates the JVM for the targeted computer type (Windows, Linux, macOS, and so on) is included with your compiled Java programs.

That’s how Java provides platform independence — and believe it or not, it works pretty well. The programs you write run just as well on a PC running any version of Windows, a Macintosh, a Unix or Linux machine, or any other computer that has a compatible JVM — including smartphones or tablet computers.

While you lie awake tonight pondering the significance of Java’s platform independence, here are a few additional thoughts to ponder:

  • Platform independence goes only so far. If you have some obscure type of computer system — such as an antique Olivetti Programma 101 — and a JVM runtime environment isn’t available for it, you can’t run Java programs on it.

    Technical stuff I didn’t make up the Olivetti Programma 101. It was a desktop computer made in the early 1960s, and it happened to be my introduction to computer programming. (My junior high school math teacher had one in the back of his classroom, and he let me play with it during lunch.) Do a Google search for “Olivetti Programma 101” and you can find several interesting websites about it.

  • Java’s platform independence isn’t perfect. Although the bytecode runs identically on every computer that has a JVM, some parts of Java use services provided by the underlying operating system. As a result, minor variations sometimes crop up, especially in applications that use graphical interfaces.
  • Because a runtime system that emulates a JVM executes Java bytecode, some people mistakenly compare Java with interpreted languages such as Basic or Perl. Those languages aren’t compiled at all, however. Instead, the interpreter reads and interprets each statement as it is executed. Java is a true compiled language; it’s just compiled to the machine language of JVM rather than to the machine language of an actual computer platform.

  • Technical stuff If you’re interested, the JVM is completely stack-oriented; it has no registers for storing local data. (I’m not going to explain what that term means, so if it doesn’t make sense to you, skip it. It’s not important. It’s just interesting to nerds who know about stacks, registers, and things of that ilk.)

Object orientation

Java is inherently object-oriented, which means that Java programs are made up from programming elements called objects. Simply put (don’t you love it when you read that in a computer book?), an object is a programming entity that represents either some real-world object or an abstract concept.

All objects have two basic characteristics:

  • Objects have data, also known as state. An object that represents a book, for example, has data such as the book’s title, author, and publisher.
  • Objects also have behavior, which means that they can perform certain tasks. In Java, these tasks are called methods. An object that represents a car might have methods such as start, stop, drive, and crash. Some methods simply allow you to access the object's data. A book object might have a getTitle method that tells you the book’s title.

Classes are closely related to objects. A class is the program code you write to create objects. The class describes the data and methods that define the object’s state and behavior. When the program executes, classes are used to create objects.

Suppose you’re writing a payroll program. This program probably needs objects to represent the company’s employees. So the program includes a class (probably named Employee) that defines the data and methods for each Employee object. When your program runs, it uses this class to create an object for each of your company's employees.

The Java API

The Java language itself is very simple, but Java comes with a library of classes that provide commonly used utility functions that most Java programs can’t do without. This class library, called the Java API (short for application programming interface), is as much a part of Java as the language itself. In fact, the real challenge of finding out how to use Java isn’t mastering the language; it’s mastering the API. The Java language has only about 50 keywords, but the Java API has several thousand classes, with tens of thousands of methods that you can use in your programs.

The Java API has classes that let you do trigonometry, write data to files, create windows onscreen, and retrieve information from a database, among other things. Many of the classes in the API are general purpose and commonly used. A whole series of classes stores collections of data, for example. But many are obscure, used only in special situations.

Fortunately, you don’t have to learn anywhere near all of the Java API. Most programmers are fluent with only a small portion of it: the portion that applies most directly to the types of programs they write. If you find a need to use some class from the API that you aren’t yet familiar with, you can look up what the class does in the Java API documentation at http://docs.oracle.com/en/java/javase/14.

The Internet

Java is often associated with the Internet, and rightfully so, because Al Gore invented Java just a few days after he invented the Internet. Okay, Java wasn’t really invented by Al Gore. It was developed right at the time the World Wide Web was becoming a phenomenon, and Java was specifically designed to take advantage of the web. In particular, the whole concept behind the JVM is to enable any computer connected to the Internet to run Java programs, regardless of the type of computer or the operating system it runs.

Most Java programming on the Internet uses servlets, which are web-based Java programs that run on an Internet server computer rather than in an Internet user’s web browser.

A servlet generates a page of HTML and JavaScript that is sent to a user’s computer to be displayed in the user’s web browser. If you request information about a product from an online store, the store’s web server runs a servlet to generate the HTML page containing the product information you requested.

Java versus Other Languages

Superficially, Java looks a lot like many of the programming languages that preceded it, most notably C and C++. For example, here’s the classic Hello, World! program, written in the C programming language:

main()

{

printf("Hello, World!");

}

This program simply displays the text "Hello, World!" on the computer's console. Here’s the classic Hello, World! program written in Java:

public class HelloApp

{

public static void main(String[] args)

{

System.out.println("Hello, World!");

}

}

Although the Java version is a bit more verbose, the two have several similarities:

  • Both require each executable statement to end with a semicolon (;).
  • Both use braces ({}) to mark blocks of code.
  • Both use a routine called main as the main entry point for the program.

Many other similarities aren't evident in these simple examples, but the examples bring the major difference between C and Java front and center: Object-oriented programming rears its ugly head even in simple examples. Consider the following points:

  • In Java, even the simplest program is a class, so you have to provide a line that declares the name of the class. In this example, the class is named HelloApp. HelloApp has a method named main, which the JVM automatically calls when a program is run.

  • In the C example, printf is a library function you call to print information to the console. In Java, you use the PrintStream class to write information to the console.

    PrintStream? There's no PrintStream in this program! Wait a minute — yes, there is. Every Java program has available to it a PrintStream object that writes information to the console. You can get this PrintStream object by calling the out method of another class, named System. Thus, System.out gets the PrintStream object that writes to the console. The PrintStream class in turn has a method named println that writes a line to the console. So System.out.println really does two things, in the following order:

    1. It uses the out field of the System class to get a PrintStream object.
    2. It calls the println method of that object to write a line to the console.

    Confusing? You bet. Everything will make sense, however, when you read about object-oriented programming in Book 3, Chapter 1.

  • void looks familiar. Although it isn't shown in the C example, you could have coded void on the main function declaration to indicate that the main function doesn’t return a value. void has the same meaning in Java. But static? What does that mean? That, too, is evidence of Java's object orientation. It’s a bit early to explain what it means in this chapter, but you can find out in Book 2, Chapter 7.

Important Features of the Java Language

If you believe the marketing hype put out by Oracle and others, you think that Java is the best thing to happen to computers since the invention of memory. Java may not be that revolutionary, but it does have many built-in features that set it apart from other languages. The following sections describe just three of the many features that make Java so popular.

Type checking

All programming languages must deal in one way or the other with type checking — the way that a language handles variables that store different types of data. Numbers, strings, and dates, for example, are commonly used data types available in most programming languages. Most programming languages also have several types of numbers, such as integers and real numbers.

All languages must check data types, so make sure that you don’t try to do things that don’t make sense (such as multiplying the gross national product by your last name). The question is, does the language require you to declare every variable’s type so you can do type checking when it compiles your programs, or does the language do type checking only after it runs your program?

Some languages, such as Perl, are not as rigid about type checking as Java. For example, Perl does not require that you indicate whether a variable will contain an integer, a floating point number, or a string. Thus, all the following statements are allowed for a single variable named $a:

$a = 5

$a = "Strategery"

$a = 3.14159

Here three different types of data — integer, string, and double — have been assigned to the same variable.

Java, on the other hand, does complete type checking when the program is compiled. As a result, you must declare all variables as a particular type so that the compiler can make sure you use the variables correctly. The following bit of Java code, for example, won’t compile:

int a = 5;

String b = "Strategery";

String c = a * b;

If you try to compile these lines, you get an error message saying that Java can’t multiply an integer and a string.

In Java, every class you define creates a new type of data for the language to work with. Thus, the data types you have available to you in Java aren’t just simple predefined types, such as numbers and strings. You can create your own types. If you’re writing a payroll system, you might create an Employee type. Then you can declare variables of type Employee that can hold only Employee objects. This capability prevents a lot of programming errors. Consider this code snippet:

Employee newHire;

newHire = 21;

This code creates a variable (newHire) that can hold only Employee objects. Then it tries to assign the number 21 to it. The Java compiler won't let you run this program because 21 is a number, not an employee.

Technical stuff An important object-oriented programming feature of Java called inheritance adds an interesting — and incredibly useful — twist to type checking. Inheritance is way too complicated to dive into just yet, so I’ll be brief here: In Java, you can create your own data types that are derived from other data types. Employees are people, for example, and customers are people too, so you might create a Person class and then create Employee and Customer classes that both inherit the Person class. Then you can write code like this:

Person p;

Employee e;

Customer c;

p = e; // This is allowed because an Employee is also a Person.

c = e; // This is not allowed because an Employee is not a Customer.

Confused yet? If so, that's my fault. Inheritance is a pretty heady topic for Chapter 1 of a Java book. Don’t panic if it makes no sense just yet. It will all be clear by the time you finish reading Book 3, Chapter 4, which covers all the subtle nuances of using inheritance.

Exception handling

As Robert Burns said, “The best-laid schemes o’ mice an’ men gang oft agley, an’ lea’e us nought but grief an’ pain, for promis’d joy!” When you tinker with computer programming, you’ll quickly discover what he meant. No matter how carefully you plan and test your programs, errors happen, and when they do, they threaten to bring your whole program to a crashing halt.

Java has a unique approach to error handling that’s superior (in my opinion) to that of any other language (except C#, which just copies Java’s approach, as I mention earlier in the chapter). In Java, the JRE intercepts and folds errors of all types into a special type of object called an exception object. After all, Java is object-oriented through and through, so why shouldn’t its exception-handling features be object-oriented?

Java requires any statements that can potentially cause an exception to be bracketed by code that can catch and handle the exception. In other words, you, as the programmer, must anticipate errors that can happen while your program is running and make sure that those errors are dealt with properly. Although this necessity can be annoying, it makes the resulting programs more reliable.

On the Downside: Java’s Weaknesses

So far, I’ve been tooting Java’s horn pretty loudly. Lest you think that figuring out how to use it is a walk in the park, the following paragraphs point out some of Java’s shortcomings (many of which have to do with the API rather than the language itself):

  • The API is way too big. It includes so many classes and methods that you’ll likely never use even half of them. Also, the sheer size of the Java API doesn’t allow you to wander through it on your own, hoping to discover the one class that’s perfect for the problem you’re working on.
  • The API is overdesigned. In some cases, it seems as though the Java designers go out of their way to complicate things that should be simple to use. For example, the API class that defines a multiline text-input area doesn’t have a scroll bar. Instead, a separate class defines a panel that has a scroll bar. To create a multiline text area with a scroll bar, you have to use both classes. It would be simpler if there were an option on the multi-line text area class that let you specify whether you wanted to include a scroll bar.
  • Some corners of the API are haphazardly designed. Most of the problems can be traced back to the initial version of Java, which was rushed to market so that it could ride the crest of the World Wide Web wave in the late 1990s. Since then, many parts of the API have been retooled more thoughtfully, but the API is still riddled with remnants of Java’s early days.

  • Technical stuff In my opinion, the biggest weakness of Java is that it doesn’t have a decimal data type. This issue is a little too complicated to get into right now, but the implication is this: Without special coding (which few Java books explain and few Java programmers realize), Java doesn’t know how to add. Consider this bit of code:

    double x = 5.02;

    double y = 0.01;

    double z = x + y;

    System.out.println(z);

    This little program should print 5.03, right? It doesn’t. Instead, it prints 5.029999999999999. This little error may not seem like much, but it can add up. If you ever make a purchase from an online store and notice that the sales tax is a penny off, this is why. The explanation for why these errors happen — and how to prevent them — is pretty technical, but it's something that every Java programmer needs to understand.

    For the scoop on how to avoid this problem, refer to Book 2, Chapter 3.

Java Version Insanity

Like most products, Java gets periodic upgrades and enhancements. Since its initial release in 1996, Java has undergone the following version updates:

  • Java 1.0: This version was the original version of Java, released in 1996. Most of the language is still pretty much the same as it was in version 1.0, but the API has changed a lot since this release.
  • Java 1.1: This version was the first upgrade to Java, released in 1997. This release is important because most Internet browsers include built-in support for applets based on Java 1.1. To run applets based on later versions of Java, in most cases you must download and install a current JRE.
  • Java 1.2: This version, released in late 1998, was a huge improvement over the previous version — so much so, in fact, that Sun called it Java 2. It included an entirely new API called Swing for creating graphical user interfaces, as well as other major features.
  • Java 1.3: This version, released in 2000, was mostly about improving performance by changing the way the runtime system works. Oddly, though this version is technically Java 1.3, it’s also called Java 2 version 1.3. Go figure.
  • Java 1.4: Released in 2001, this version offered a slew of improvements. As you might guess, it’s called Java 2 version 1.4. Keep figuring….

  • Java 5.0: Released in 2004, this version included more changes and improvements than any other version. To add to Sun’s apparent unpredictability in its version numbering, this version officially has two version numbers. Sun’s official Java website explains it like this:

    • Both version numbers “1.5.0” and “5.0” are used to identify this release of the Java 2 Platform Standard Edition. Version “5.0” is the product version, while “1.5.0” is the developer version.

    That clears everything right up, doesn’t it?

  • Java 6.0: Released in December 2006 (just in time for the holidays!), this version of Java offered minor improvements and better efficiency.

    For Java 1.6, the product version is 6 (not 6.0). Remember the extra 2 that appeared magically in 1998? Well, the 2 is gone in Java 1.6. So unlike the versions between 1998 and 2006, Java 1.6 is officially named the Java Platform (not the Java 2 Platform). Personally, I think someone at Sun has been talking to George Lucas. I fully expect the next version of Java to be a prequel called Java 0 Episode 1.

  • Java 7.0: Released in mid-2011, this was a relatively minor upgrade that added a few enhancements to the API and a few tweaks to the language itself.
  • Java 8.0: Released in February 2014, Java 8 (as it is known) adds some significant and long-anticipated new features to Java. One of the most important is lambda expressions, a language feature that simplifies certain aspects of object-oriented programming. Other new features include a completely revamped API for working with dates and times, and a new framework for working with large collections of data in a way that can easily take advantage of multicore processors.
  • Java 9.0: Released in 2017, Java 9 adds a significant and long-awaited feature called the Java Module System, which provides a new and improved way of managing the collections of Java code that make up a complete Java application and dramatically changes how Java applications are packaged. You learn about this new feature in Book 3, Chapter 8.
  • Java 10.0: Released in March 2018, this version is the first to be released under the a new development schedule, in which new releases will come out twice per year, first in March and then in September.
  • Java 11.0: Released in September 2018, this version introduced a dozen new features. The most popular is the local type inference, which introduces the var keyword (well, technically not a keyword but it sure looks and acts like a keyword), which allows the compiler to infer the type of a variable from its context.
  • Java 12.0: Released in March 2019, this version introduced a dozen or so minor features, including a new standardized web client, which is covered in Book 7, Chapter 5.
  • Java 13.0: Released in September 2019, this version introduced, among other things, a long-needed improvement to the switch statement, which I cover in Book 2, Chapter 6.
  • Java 14.0: Released in March 2020, this is the current version as of the writing of this book. It includes a new type of data structure, called a Record, which I cover in Book 3, Chapter 2.

What’s in a Name?

The final topic that I want to cover in this chapter is the names of the various pieces that make up Java’s technology — specifically, the acronyms you constantly come across whenever you read or talk about Java, such as JVM, JRE, JDK, and J2EE. Here they are, in no particular order of importance:

  • JDK: Java Development Kit — that is, the toolkit for developers that includes the Java compiler and the runtime environment. To write Java programs, you need the JDK. This term was used with the original versions of Java (1.0 and 1.1) and abandoned with version 1.2 in favor of SDK. But with versions 5.0, the term reappeared and is still in use today.
  • SDK: Software Development Kit — what Sun called the JDK for versions 1.2, 1.3, and 1.4.
  • JRE: Java Runtime Environment — the program that emulates the JVM so that users can run Java programs. To run Java programs, you need only download and install the JRE. Prior to Java 11, this was a separately installable program that had to be installed on computers that ran Java programs. This is no longer the case; the runtime environment is now packaged with executable Java applications.
  • JVM: Java Virtual Machine — the platform-independent machine that’s emulated by the JRE. All Java programs run in a JVM.
  • Java SE: Java Standard Edition — a term that describes the Java language and the basic set of API libraries that are used to create Java programs that can run on Windows, Linux, and other platforms, such as Macintosh. Most of this book focuses on Java SE.
  • J2SE: Java 2 Standard Edition — an older term for the Java language and basic libraries (for Java versions 1.2 through 1.5).
  • Java EE: Java Enterprise Edition, also known as J2EE (Java 2 Enterprise Edition) — an expanded set of API libraries that provide special functions such as servlets.