Overview of the Java Programming Language
Overview of the Java Programming Language
Java gained popularity shortly after its release, and has been a popular programming language
since then.[19] Java was the third most popular programming language in 2022 according to
GitHub.[20] Although still widely popular, there has been a gradual decline in use of Java in recent
years with other languages using JVM gaining popularity.[21]
Java was designed by James Gosling at Sun Microsystems. It was released in May 1995 as a core
component of Sun's Java platform. The original and reference implementation Java compilers,
virtual machines, and class libraries were released by Sun under proprietary licenses. As of May
2007, in compliance with the specifications of the Java Community Process, Sun had relicensed
most of its Java technologies under the GPL-2.0-only license. Oracle, which bought Sun in 2010,
offers its own HotSpot Java Virtual Machine. However, the official reference implementation is the
OpenJDK JVM, which is open-source software used by most developers and is the default JVM for
almost all Linux distributions.
Java 25 is the version current as of September 2025. Java 8, 11, 17, 21, and 25 are long-term
support versions still under maintenance.
History Java
Paradigm Multi-paradigm:
Duke, the Java
generic, object-
mascot
oriented (class-
based), functional,
imperative, reflective,
concurrent
James Gosling, Mike Sheridan, and Patrick Typing discipline Static, strong, safe,
nominative, manifest
Naughton initiated the Java language project in
June 1991.[22] Java was originally designed for Memory Garbage-collected
interactive television, but it was too advanced for management
In 1997, Sun Microsystems approached the ISO/IEC JTC 1 standards body and later the Ecma
International to formalize Java, but it soon withdrew from the process.[28][29][30] Java remains a de
facto standard, controlled through the Java Community Process.[31] At one time, Sun made most of
its Java implementations available without charge, despite their proprietary software status. Sun
generated revenue from Java through the selling of licenses for specialized products such as the
Java Enterprise System.
On November 13, 2006, Sun released much of its Java virtual machine (JVM) as free and open-
source software (FOSS), under the terms of the GPL-2.0-only license. On May 8, 2007, Sun finished
the process, making all of its JVM's core code available under free software/open-source
distribution terms, aside from a small portion of code to which Sun did not hold the copyright.[32]
Sun's vice-president Rich Green said that Sun's ideal role with regard to Java was as an
evangelist.[33] Following Oracle Corporation's acquisition of Sun Microsystems in 2009–10, Oracle
has described itself as the steward of Java technology with a relentless commitment to fostering a
community of participation and transparency.[34] This did not prevent Oracle from filing a lawsuit
against Google shortly after that for using Java inside the Android SDK (see the Android section).
On April 2, 2010, James Gosling resigned from Oracle.[35]
In January 2016, Oracle announced that Java run-time environments based on JDK 9 will
discontinue the browser plugin.[36]
Java software runs on most devices from laptops to data centers, game consoles to scientific
supercomputers.[37]
Oracle (and others) highly recommend uninstalling outdated and unsupported versions of Java, due
to unresolved security issues in older versions.[38]
Principles
Versions
As of September 2025, Java 8, 11, 17, 21, and 25 are supported as long-term support (LTS)
versions.[39]
Oracle released the last zero-cost public update for the legacy version Java 8 LTS in January 2019
for commercial use, although it will otherwise still support Java 8 with public updates for personal
use indefinitely. Other vendors such as Adoptium continue to offer free builds of OpenJDK's long-
term support (LTS) versions. These builds may include additional security patches and bug fixes.[40]
Editions
Sun has defined and supports four editions of Java targeting different application environments and
segmented many of its APIs so that they belong to one of the platforms. The platforms are:
Java Platform, Enterprise Edition (Java EE) – targeting large distributed enterprise or Internet
environments.[50]
The classes in the Java APIs are organized into separate groups called packages. Each package
contains a set of related interfaces, classes, subpackages and exceptions.
Sun also provided an edition called Personal Java that has been superseded by later, standards-
based Java ME configuration-profile pairings.
Execution system
One design goal of Java is portability, which means that programs written for the Java platform
must run similarly on any combination of hardware and operating system with adequate run time
support. This is achieved by compiling the Java language code to an intermediate representation
called Java bytecode, instead of directly to architecture-specific machine code. Java bytecode
instructions are analogous to machine code, but they are intended to be executed by a virtual
machine (VM) written specifically for the host hardware. End-users commonly use a Java Runtime
Environment (JRE) installed on their device for standalone Java applications or a web browser for
Java applets.
Standard libraries provide a generic way to access host-specific features such as graphics,
threading, and networking.
The use of universal bytecode makes porting simple. However, the overhead of interpreting
bytecode into machine instructions made interpreted programs almost always run more slowly than
native executables. Just-in-time (JIT) compilers that compile byte-codes to machine code during
runtime were introduced from an early stage. Java's Hotspot compiler is actually two compilers in
one; and with GraalVM (included in e.g. Java 11, but removed as of Java 16) allowing tiered
compilation.[51] Java itself is platform-independent and is adapted to the particular platform it is to
run on by a Java virtual machine (JVM), which translates the Java bytecode into the platform's
machine language.[52]
Performance
Programs written in Java have a reputation for being slower and requiring more memory than those
written in C++.[53][54] However, Java programs' execution speed improved significantly with the
introduction of just-in-time compilation in 1997/1998 for Java 1.1,[55] the addition of language
features supporting better code analysis (such as inner classes, the StringBuilder class, optional
assertions, etc.), and optimizations in the Java virtual machine, such as HotSpot becoming Sun's
default JVM in 2000. With Java 1.5, the performance was improved with the addition of the
[Link] package, including lock-free implementations of the ConcurrentMaps
and other multi-core collections, and it was improved further with Java 1.6.
Non-JVM
Some platforms offer direct hardware support for Java; there are micro controllers that can run Java
bytecode in hardware instead of a software Java virtual machine,[56] and some ARM-based
processors could have hardware support for executing Java bytecode through their Jazelle option,
though support has mostly been dropped in current implementations of ARM.
Java uses an automatic garbage collector to manage memory in the object lifecycle. The
programmer determines when objects are created, and the Java runtime is responsible for
recovering the memory once objects are no longer in use. Once no references to an object remain,
the unreachable memory becomes eligible to be freed automatically by the garbage collector.
Something similar to a memory leak may still occur if a programmer's code holds a reference to an
object that is no longer needed, typically when objects that are no longer needed are stored in
containers that are still in use.[57] If methods for a non-existent object are called, a null pointer
exception is thrown.[58][59]
One of the ideas behind Java's automatic memory management model is that programmers can be
spared the burden of having to perform manual memory management. In some languages, memory
for the creation of objects is implicitly allocated on the stack or explicitly allocated and deallocated
from the heap. In the latter case, the responsibility of managing memory resides with the
programmer. If the program does not deallocate an object, a memory leak occurs.[57] If the program
attempts to access or deallocate memory that has already been deallocated, the result is undefined
and difficult to predict, and the program is likely to become unstable or crash. This can be partially
remedied by the use of smart pointers, but these add overhead and complexity. Garbage collection
does not prevent logical memory leaks, i.e. those where the memory is still referenced but never
used.[57]
Garbage collection may happen at any time. Ideally, it will occur when a program is idle. It is
guaranteed to be triggered if there is insufficient free memory on the heap to allocate a new object;
this can cause a program to stall momentarily. Explicit memory management is not possible in
Java.
Java does not support C/C++ style pointer arithmetic,[60] where object addresses can be
arithmetically manipulated (e.g. by adding or subtracting an offset). This allows the garbage
collector to relocate referenced objects and ensures type safety and security.
As in C++ and some other object-oriented languages, variables of Java's primitive data types are
either stored directly in fields (for objects) or on the stack (for methods) rather than on the heap, as
is commonly true for non-primitive data types (but see escape analysis). This was a conscious
decision by Java's designers for performance reasons.
Java contains multiple types of garbage collectors. Since Java 9, HotSpot uses the Garbage First
Garbage Collector (G1GC) as the default.[61] However, there are also several other garbage
collectors that can be used to manage the heap, such as the Z Garbage Collector (ZGC) introduced
in Java 11, and Shenandoah GC, introduced in Java 12 but unavailable in Oracle-produced OpenJDK
builds. Shenandoah is instead available in third-party builds of OpenJDK, such as Eclipse Temurin.
For most applications in Java, G1GC is sufficient. In prior versions of Java, such as Java 8, the
Parallel Garbage Collector ([Link]
[Link]) was used as the default garbage collector.
Having solved the memory management problem does not relieve the programmer of the burden of
handling properly other kinds of resources, like network or database connections, file handles, etc.,
especially in the presence of exceptions.
Syntax
The syntax of Java is largely influenced by C++ and C. Unlike C++, which combines the syntax for
structured, generic, and object-oriented programming, Java was built almost exclusively as an
object-oriented language.[18] All code is written inside classes, and every data item is an object, with
the exception of the primitive data types, (i.e. integers, floating-point numbers, boolean values, and
characters), which are not objects for performance reasons.
Unlike C++, Java does not support operator overloading[62] or multiple inheritance for classes,
though multiple inheritance is supported for interfaces.[63]
Java uses comments similar to those of C++. There are three different styles of comments: a single
line style marked with two slashes ( // ), a multiple line style opened with /* and closed with */ ,
and the Javadoc commenting style opened with /** and closed with */ . The Javadoc style of
commenting allows the user to run the Javadoc executable to create documentation for the
program and can be read by some integrated development environments (IDEs) such as Eclipse to
allow developers to access documentation within the IDE.
Hello world
The following is an example of a "Hello, World!" program in the traditional Java syntax:
Java 25 introduced a simplified syntax for the main class and main method, which enables users to
write small Java programs succinctly:[64][65]
1 void main() {
2 [Link]("Hello World!");
3 }
Special classes
Applet
Java applets were programs embedded in other applications, mainly in web pages displayed in web
browsers. The Java applet API was deprecated with the release of Java 9 in 2017.[66][67]
Servlet
Java servlet technology provides Web developers with a simple, consistent mechanism for
extending the functionality of a Web server and for accessing existing business systems. Servlets
are server-side Java EE components that generate responses to requests from clients. Most of the
time, this means generating HTML pages in response to HTTP requests, although there are a
number of other standard servlet classes available, for example for WebSocket communication.
The Java servlet API has to some extent been superseded (but still used under the hood) by two
standard Java technologies for web services:
the Java API for RESTful Web Services (JAX-RS 2.0) useful for AJAX, JSON and REST services,
and
the Java API for XML Web Services (JAX-WS) useful for SOAP Web Services.
Typical implementations of these APIs on Application Servers or Servlet Containers use a standard
servlet for handling all interactions with the HTTP requests and responses that delegate to the web
service methods for the actual business logic.
JavaServer Pages
JavaServer Pages (JSP) are server-side Java EE components that generate responses, typically
HTML pages, to HTTP requests from clients. JSPs embed Java code in an HTML page by using the
special delimiters <% and %> . A JSP is compiled to a Java servlet, a Java application in its own
right, the first time it is accessed. After that, the generated servlet creates the response.[68]
Swing application
Swing is a graphical user interface library for the Java SE platform. It is possible to specify a
different look and feel through the pluggable look and feel system of Swing. Clones of Windows,
GTK+, and Motif are supplied by Sun. Apple also provides an Aqua look and feel for macOS. Where
prior implementations of these looks and feels may have been considered lacking, Swing in Java SE
6 addresses this problem by using more native GUI widget drawing routines of the underlying
platforms.[69]
JavaFX application
JavaFX is a software platform for creating and delivering desktop applications, as well as rich web
applications that can run across a wide variety of devices. JavaFX is intended to replace Swing as
the standard graphical user interface (GUI) library for Java SE, but since JDK 11 JavaFX has not
been in the core JDK and instead in a separate module.[70] JavaFX has support for desktop
computers and web browsers on Microsoft Windows, Linux, and macOS. JavaFX does not have
support for native OS look and feels.[71]
Generics
In 2004, generics were added to the Java language, as part of J2SE 5.0. Prior to the introduction of
generics, each variable declaration had to be of a specific type. For container classes, for example,
this is a problem because there is no easy way to create a container that accepts only specific types
of objects. Either the container operates on all subtypes of a class or interface, usually Object , or
a different container class has to be created for each contained class. Generics allow compile-time
type checking without having to create many container classes, each containing almost identical
code. In addition to enabling more efficient code, certain runtime exceptions are prevented from
occurring, by issuing compile-time errors. If Java prevented all runtime type errors
( ClassCastException s) from occurring, it would be type safe.
In 2016, the type system of Java was proven unsound in that it is possible to use generics to
construct classes and methods that allow assignment of an instance of one class to a variable of
another unrelated class. Such code is accepted by the compiler, but fails at run time with a class
cast exception.[72]
Criticism
Criticisms directed at Java include the implementation of generics,[73] speed,[53] the handling of
unsigned numbers,[74] the implementation of floating-point arithmetic,[75] and a history of security
vulnerabilities in the primary Java VM implementation HotSpot.[76] Developers have criticized the
complexity and verbosity of the Java Persistence API (JPA), a standard part of Java EE. This has led
to increased adoption of higher-level abstractions like Spring Data JPA, which aims to simplify
database operations and reduce boilerplate code. The growing popularity of such frameworks
suggests limitations in the standard JPA implementation's ease-of-use for modern Java
development.
Class libraries
The Java Class Library is the standard library, developed to support application development in
Java. It is controlled by Oracle in cooperation with others through the Java Community Process
program.[77] Companies or individuals participating in this process can influence the design and
development of the APIs. This process has been a subject of controversy during the 2010s.[78] The
class library contains features such as:
Generics
Scripting, Compiler
Security[84]
The integration libraries, which allow the application writer to communicate with external
systems. These libraries include:
The Java Database Connectivity (JDBC) API for database access
Java Naming and Directory Interface (JNDI) for lookup and discovery
Java remote method invocation (RMI) and Common Object Request Broker Architecture
(CORBA) for distributed application development
The (lightweight) Swing libraries, which are built on AWT but provide (non-native)
implementations of the AWT widgetry
JavaFX
A platform dependent implementation of the Java virtual machine that is the means by which the
bytecodes of the Java libraries and third-party applications are executed
Java Web Start, which allows Java applications to be efficiently distributed to end users across
the Internet
Documentation
Implementations
Oracle Corporation owns the official implementation of the Java SE platform, due to its acquisition
of Sun Microsystems on January 27, 2010. This implementation is based on the original
implementation of Java by Sun. The Oracle implementation is available for Windows, macOS, Linux,
and Solaris. Because Java lacks any formal standardization recognized by Ecma International,
ISO/IEC, ANSI, or other third-party standards organizations, the Oracle implementation is the de
facto standard.
The Oracle implementation is packaged into two different distributions: The Java Runtime
Environment (JRE) which contains the parts of the Java SE platform required to run Java programs
and is intended for end users, and the Java Development Kit (JDK), which is intended for software
developers and includes development tools such as the Java compiler, Javadoc, Jar, and a
debugger. Oracle has also released GraalVM, a high performance Java dynamic compiler and
interpreter.
OpenJDK is another Java SE implementation that is licensed under the GNU GPL. The
implementation started when Sun began releasing the Java source code under the GPL. As of Java
SE 7, OpenJDK is the official Java reference implementation.
The goal of Java is to make all implementations of Java compatible. Historically, Sun's trademark
license for usage of the Java brand insists that all implementations be compatible. This resulted in
a legal dispute with Microsoft after Sun claimed that the Microsoft implementation did not support
Java remote method invocation (RMI) or Java Native Interface (JNI) and had added platform-
specific features of their own. Sun sued in 1997, and, in 2001, won a settlement of US$20 million, as
well as a court order enforcing the terms of the license from Sun.[87] As a result, Microsoft no longer
ships Java with Windows.
Platform-independent Java is essential to Java EE, and an even more rigorous validation is required
to certify an implementation. This environment enables portable server-side applications.
The Java programming language requires the presence of a software platform in order for compiled
programs to be executed.
Oracle supplies the Java platform for use with Java. The Android SDK is an alternative software
platform, used primarily for developing Android applications with its own GUI system.
Android
The Java language is a key pillar in Android, an open source mobile operating system. Although
Android, built on the Linux kernel, is written largely in C, the Android SDK uses the Java language as
the basis for Android applications but does not use any of its standard GUI, SE, ME or other
established Java standards.[88] The bytecode language supported by the Android SDK is
incompatible with Java bytecode and runs on its own virtual machine, optimized for low-memory
devices such as smartphones and tablet computers. Depending on the Android version, the
bytecode is either interpreted by the Dalvik virtual machine or compiled into native code by the
Android Runtime.
Android does not provide the full Java SE standard library, although the Android SDK does include
an independent implementation of a large subset of it. It supports Java 6 and some Java 7 features,
offering an implementation compatible with the standard library (Apache Harmony).
Controversy
The use of Java-related technology in Android led to a legal dispute between Oracle and Google. On
May 7, 2012, a San Francisco jury found that if APIs could be copyrighted, then Google had infringed
Oracle's copyrights by the use of Java in Android devices.[89] District Judge William Alsup ruled on
May 31, 2012, that APIs cannot be copyrighted,[90] but this was reversed by the United States Court
of Appeals for the Federal Circuit in May 2014.[91] On May 26, 2016, the district court decided in
favor of Google, ruling the copyright infringement of the Java API in Android constitutes fair use.[92]
In March 2018, this ruling was overturned by the Appeals Court, which sent down the case of
determining the damages to federal court in San Francisco.[93] Google filed a petition for writ of
certiorari with the Supreme Court of the United States in January 2019 to challenge the two rulings
that were made by the Appeals Court in Oracle's favor.[94] On April 5, 2021, the Court ruled 6–2 in
Google's favor, that its use of Java APIs should be considered fair use. However, the court refused
to rule on the copyrightability of APIs, choosing instead to determine their ruling by considering
Java's API copyrightable "purely for argument's sake."[95]
See also
C#
C++ Computer
programming portal
Dalvik, used in old Android versions, replaced by non-JIT Android
Runtime
References
3. Barbara Liskov with John Guttag (2000). Program Development in Java – Abstraction,
Specification, and Object-Oriented Design. USA, Addison Wesley. ISBN 978-0-201-65768-5.
4. Chaudhary, Harry H. (July 28, 2014). "Cracking The Java Programming Interview :: 2000+ Java
Interview Que/Ans" ([Link] .
Archived ([Link]
=0rUtBAAAQBAJ&pg=PAPA133#v=onepage&q&f=false) from the original on September 29,
2023. Retrieved May 29, 2016.
5. Java 5.0 added several new language features (the enhanced for loop, autoboxing, varargs and
annotations), after they were introduced in the similar (and competing) C# language. [1] (http://
[Link]/papers/java5/) Archived ([Link]
65438/[Link] March 19, 2011, at the Wayback
Machine [2] ([Link] Archived ([Link]
7162045/[Link] January 7, 2006, at the Wayback Machine
6. Gosling, James; McGilton, Henry (May 1996). "The Java Language Environment" ([Link]
[Link]/technetwork/java/[Link]) . Archived ([Link]
20140506214653/[Link] from the
original on May 6, 2014. Retrieved May 6, 2014.
7. Gosling, James; Joy, Bill; Steele, Guy; Bracha, Gilad. "The Java Language Specification, 2nd
Edition" ([Link] .
Archived ([Link]
second_edition/html/[Link]#237601) from the original on August 5, 2011. Retrieved
February 8, 2008.
9. Niklaus Wirth stated on a number of public occasions, e.g. in a lecture at the Polytechnic
Museum, Moscow in September 2005 (several independent first-hand accounts in Russian
exist, e.g. one with an audio recording: Filippova, Elena (September 22, 2005). "Niklaus Wirth's
lecture at the Polytechnic Museum in Moscow" ([Link]
asp?catalogid=1155) . Archived ([Link]
[Link]/asp/[Link]?catalogid=1155) from the original on December 1,
2020. Retrieved November 20, 2011.), that the Sun Java design team licensed the Oberon
compiler sources a number of years prior to the release of Java and examined it: a (relative)
compactness, type safety, garbage collection, no multiple inheritance for classes – all these
key overall design features are shared by Java and Oberon.
10. Patrick Naughton cites Objective-C as a strong influence on the design of the Java
programming language, stating that notable direct derivatives include Java interfaces (derived
from Objective-C's protocol) and primitive wrapper classes. [3] ([Link]
f/[Link]) Archived ([Link]
u/~sean/stuff/[Link]) July 13, 2011, at the Wayback Machine
11. TechMetrix Research (1999). "History of Java" ([Link]
2/[Link] (PDF). Java Application Servers Report.
Archived from the original ([Link] (PDF) on December
29, 2010. "The project went ahead under the name green and the language was based on an
old model of UCSD Pascal, which makes it possible to generate interpretive code."
16. "Facebook Q&A: Hack brings static typing to PHP world" ([Link]
10885/[Link]) . InfoWorld. March 26,
2014. Archived ([Link]
cle/2610885/[Link]) from the original on
February 13, 2015. Retrieved January 11, 2015.
19. Melanson, Mike (August 9, 2022). "Don't call it a comeback: Why Java is still champ" ([Link]
[Link]/readme/featured/java-programming-language) . GitHub. Archived ([Link]
[Link]/web/20230825195416/[Link]
ge) from the original on August 25, 2023. Retrieved October 15, 2023.
21. McMillan, Robert (August 1, 2013). "Is Java Losing Its Mojo?" ([Link]
1/java-no-longer-a-favorite/) . Wired. Archived ([Link]
9/[Link] from the original on February
15, 2017. Retrieved October 15, 2023.
22. Byous, Jon (c. 1998). "Java technology: The early years" ([Link]
20081440/[Link] . Sun Developer Network.
Sun Microsystems. Archived from the original ([Link]
[Link]) on April 20, 2005. Retrieved April 22, 2005.
24. Murphy, Kieron (October 4, 1996). "So why did they decide to call it Java?" ([Link]
[Link]/article/2077265/[Link]) . JavaWorld. Archived (h
ttps://[Link]/web/20200713234202/[Link]
-[Link]) from the original on July 13, 2020. Retrieved
July 13, 2020.
38. "Why should I uninstall older versions of Java from my system?" ([Link]
wnload/faq/remove_olderversions.xml) . Oracle. Archived ([Link]
0212011608/[Link] from the
original on February 12, 2018. Retrieved September 24, 2021.
43. Chander, Sharat (September 15, 2020). "The Arrival of Java 15!" ([Link]
platform-group/the-arrival-of-java-15) . Oracle. Archived ([Link]
16092332/[Link] from the
original on September 16, 2020. Retrieved September 15, 2020.
44. "JDK 21" ([Link] . [Link]. Archived ([Link]
rg/web/20230920173515/[Link] from the original on
September 20, 2023. Retrieved September 20, 2023.
51. "Deep Dive Into the New Java JIT Compiler – Graal | Baeldung" ([Link]
al-java-jit-compiler) . [Link]. August 6, 2021. Archived ([Link]
web/20211028165746/[Link] from the original
on October 28, 2021. Retrieved October 13, 2021.
52. "Is the JVM (Java Virtual Machine) platform dependent or platform independent? What is the
advantage of using the JVM, and having Java be a translated language?" ([Link]
[Link]/[Link]/java-questions/jvm-platform-dependent/) . Programmer
Interview. Archived ([Link]
[Link]/[Link]/java-questions/jvm-platform-dependent/) from the original on
January 19, 2015. Retrieved January 19, 2015.
53. Jelovic, Dejan. "Why Java will always be slower than C++" ([Link]
211111923/[Link] . Archived from the
original ([Link] on February 11, 2008.
Retrieved February 15, 2008.
55. "Symantec's Just-In-Time Java Compiler To Be Integrated into Sun JDK 1.1" ([Link]
[Link]/web/20100628171748/[Link]
19970407_03) . Archived from the original ([Link]
[Link]?prid=19970407_03) on June 28, 2010. Retrieved August 1, 2009.
56. Salcic, Zoran; Park, Heejong; Teich, Jürgen; Malik, Avinash; Nadeem, Muhammad (July 22,
2017). "Noc-HMP: A Heterogeneous Multicore Processor for Embedded Systems Designed in
SystemJ". ACM Transactions on Design Automation of Electronic Systems. 22 (4): 73.
doi:10.1145/3073416 ([Link] . ISSN 1084-4309 ([Link]
[Link]/issn/1084-4309) . S2CID 11150290 ([Link]
D:11150290) .
60. Walter, A. (2010). Towards Certification of Java Applications for Safety Critical Projects.
Proceedings of Embedded Real-Time Software and Systems, ERTS2, 1-7.
64. Krill, Paul (September 16, 2025). "JDK 25: The new features in Java 25" ([Link]
com/article/3846172/[Link]) . InfoWorld. Retrieved
October 9, 2025.
65. Pressler, Ron; Laskey, Jim; Bierman, Gavin (July 11, 2025). "JEP 512: Compact Source Files and
Instance Main Methods" ([Link] . OpenJDK. Retrieved October 9,
2025.
69. "Trail: Creating a GUI With JFC/Swing (The Java Tutorials)" ([Link]
orial/uiswing/) . [Link]. Archived ([Link]
ttps://[Link]/javase/tutorial/uiswing/) from the original on April 29, 2020.
Retrieved May 1, 2020.
70. "Removed from JDK 11, JavaFX 11 arrives as a standalone module" ([Link]
m/article/3305073/[Link]) .
InfoWorld. September 20, 2018. Archived ([Link]
s://[Link]/article/3305073/removed-from-jdk-11-javafx-11-arrives-as-a-standalon
[Link]) from the original on October 14, 2020. Retrieved October 13, 2020.
71. "Getting Started with JavaFX: Hello World, JavaFX Style" ([Link]
_started/hello_world.htm) . JavaFX 2 Tutorials and Documentation. Oracle. Archived (https://
[Link]/web/20200802013650/[Link]
[Link]) from the original on August 2, 2020. Retrieved May 1, 2020.
73. Arnold, Ken (June 27, 2005). "Generics Considered Harmful" ([Link]
71010002142/[Link]
l) . [Link]. Archived from the original ([Link]
6/generics_consid_1.html) on October 10, 2007. Retrieved September 10, 2015.
74. Owens, Sean R. "Java and unsigned int, unsigned short, unsigned byte, unsigned long, etc. (Or
rather, the lack thereof)" ([Link]
m/player/[Link]) . Archived from the original ([Link]
ayer/[Link]) on February 20, 2009. Retrieved July 4, 2011.
75. Kahan, William (March 1, 1998). "How Java's Floating-Point Hurts Everyone Everywhere – ACM
1998 Workshop on Java (Stanford)" ([Link]
(PDF). Electrical Engineering & Computer Science, University of California at Berkeley. Archived
([Link]
[Link]) (PDF) from the original on September 5, 2012. Retrieved June 4, 2011.
77. Cadenhead, Rogers (November 20, 2017), Understanding How Java Programs Work ([Link]
[Link]/articles/[Link]?p=2832404&seqNum=4) , archived ([Link]
org/web/20210813193850/[Link]
um=4) from the original on August 13, 2021, retrieved March 26, 2019
78. Woolf, Nicky (May 26, 2016). "Google wins six-year legal battle with Oracle over Android code
copyright" ([Link]
wsuit-oracle-java-code) . The Guardian. ISSN 0261-3077 ([Link]
61-3077) . Archived ([Link]
[Link]/technology/2016/may/26/google-wins-copyright-lawsuit-oracle-java-code) from the
original on March 26, 2019. Retrieved March 26, 2019.
86. "How to Write Doc Comments for the Javadoc Tool" ([Link]
cles/java/[Link]) . Oracle Technology Network. Oracle. Archived ([Link]
[Link]/web/20141218182906/[Link]
[Link]) from the original on December 18, 2014. Retrieved December 18, 2014.
87. Niccolai, James (January 24, 2001). "Sun, Microsoft settle Java lawsuit" ([Link]
[Link]/article/2074908/[Link]) . JavaWorld. IDG News
Service. Archived ([Link]
article/2074908/[Link]) from the original on July 14, 2020.
Retrieved July 13, 2020.
88. van Gurp, Jilles (November 13, 2007). "Google Android: Initial Impressions and Criticism" (http
s://[Link]/web/20080828111808/[Link]
[Link]) . Javalobby. Archived from the original on August 28, 2008. Retrieved March 7,
2009. "Frankly, I don't understand why Google intends to ignore the vast amount of existing
implementation out there. It seems like a bad case of "not invented here" to me. Ultimately, this
will slow adoption. There are already too many Java platforms for the mobile world and this is
yet another one"
89. Mullin, Joe (May 7, 2012). "Google guilty of infringement in Oracle trial; future legal headaches
loom" ([Link]
-[Link]) . Law & Disorder. Ars Technica. Archived ([Link]
[Link]/web/20120508134916/[Link]
[Link]) from the original on May 8,
2012. Retrieved May 8, 2012.
90. Mullin, Joe (May 31, 2012). "Google wins crucial API ruling, Oracle's case decimated" ([Link]
[Link]/tech/2012/05/google-wins-crucial-api-ruling-oracles-case-decimated/) . Ars
Technica. Archived ([Link]
ech-policy/2012/05/google-wins-crucial-api-ruling-oracles-case-decimated/) from the
original on March 12, 2017. Retrieved June 1, 2012.
91. Rosenblatt, Seth (May 9, 2014). "Court sides with Oracle over Android in Java patent appeal" (h
ttps://[Link]/news/court-sides-with-oracle-over-android-in-java-patent-appeal/) .
CNET. Archived ([Link]
ourt-sides-with-oracle-over-android-in-java-patent-appeal/) from the original on May 10, 2014.
Retrieved May 10, 2014.
92. Mullin, Joe (May 26, 2016). "Google beats Oracle—Android makes "fair use" of Java APIs" (http
s://[Link]/tech-policy/2016/05/google-wins-trial-against-oracle-as-jury-finds-android
-is-fair-use/) . Ars Technica. Archived ([Link]
[Link]/tech-policy/2016/05/google-wins-trial-against-oracle-as-jury-finds-android-is-f
air-use/) from the original on January 20, 2017. Retrieved May 26, 2016.
93. Farivar, Cyrus (March 27, 2018). " "Google's use of the Java API packages was not fair," appeals
court rules" ([Link]
es-was-not-fair-appeals-court-rules/) . Ars Technica. Archived ([Link]
0190924081919/[Link]
ckages-was-not-fair-appeals-court-rules/) from the original on September 24, 2019. Retrieved
August 6, 2019.
94. Lee, Timothy (April 23, 2019). "Google asks Supreme Court to overrule disastrous ruling on API
copyrights" ([Link]
ule-disastrous-ruling-on-api-copyrights/) . Ars Technica. Archived ([Link]
b/20190423084450/[Link]
-to-overrule-disastrous-ruling-on-api-copyrights/) from the original on April 23, 2019.
Retrieved April 23, 2019.
95. "Google LLC v. Oracle America, Inc 593 U. S. ____ (2021)" ([Link]
ons/20pdf/18-956_d18f.pdf) (PDF). Archived ([Link]
0/[Link] (PDF) from the original
on April 5, 2021. Retrieved April 6, 2021.
Bibliography
Bloch, Joshua (2018). Effective Java: Programming Language Guide (Third ed.). Addison-Wesley.
ISBN 978-0-13-468599-1.
Gosling, James; Joy, Bill; Steele, Guy L. Jr.; Bracha, Gilad (2005). The Java Language Specification
([Link] (3rd ed.). Addison-Wesley. ISBN 0-321-24678-0.
Archived ([Link]
from the original on February 14, 2012. Retrieved February 8, 2019.
Gosling, James; Joy, Bill; Steele, Guy; Bracha, Gilad; Buckley, Alex (2014). The Java® Language
Specification ([Link] (PDF) (Java SE 8 ed.).
Archived ([Link]
s/se8/[Link]) (PDF) from the original on October 21, 2014. Retrieved November 18, 2014.
Lindholm, Tim; Yellin, Frank (1999). The Java Virtual Machine Specification ([Link]
docs/books/vmspec/2nd-edition/html/[Link]) (2nd ed.). Addison-Wesley.
ISBN 0-201-43294-3. Archived ([Link]
m/docs/books/vmspec/2nd-edition/html/[Link]) from the original on
September 25, 2011. Retrieved February 8, 2019.
External links
News and views from members of the Java team at Oracle ([Link]