<programming, language, portability> (After the Indonesian island, a
	source of {programming fluid}) A simple, {object-oriented},
	{distributed}, {interpreted}, robust, secure,
	{architecture-neutral}, {portable}, {multithreaded}, dynamic,
	buzzword-compliant, general-purpose programming language
	developed by {Sun Microsystems} in the early 1990's (initially for
	set-top television controllers), and released to the public in 1995.

	Java first became popular by being the earliest portable
	dynamic client-side content for the {World-Wide Web} in the
	form of {platform}-independent Java "applets". In the late
	1990's and into the 2000's it has also become very popular
	on the server side, where an entire set of {APIs} defines the {J2EE}.

	Java is both a set of public specifications (controlled by
	{Sun Microsystems} through the {JCP}) and a series of
	implementations of those specifications.

	Java is syntactially similar to {C++} without user-definable
	{operator overloading}, (though it does have {method}
	overloading), without {multiple inheritance}, and extensive
	automatic {coercions}.  It has automatic {garbage collection}.
	Java extends {C++}'s {object-oriented} facilities with those
	of {Objective C} for {dynamic method resolution}.

	Whereas programs in C++ and similar languages are compiled
	and linked to platform-specific binary executables, Java
	programs are typically compiled to portable {architecture-neutral}
	{bytecode} or ".class" files, which are run using a {Java
	Virtual Machine}.  The JVM is also called an {interpreter},
	though it is more correct to say that it uses {Just-In-Time
	Compilation} to convert the {bytecode} into {native} {machine
	code}, yielding greater efficiency than most interpreted
	languages, rivalling C++ for many long-running, non-GUI
	applications.  The run-time system is typically written in
	{POSIX}-compliant {ANSI C} or {C++}.  Some implementations
	allow Java class files to be translated into {native}
	{machine code} during or after compilation.

	The Java compiler and {linker} both enforce {strong type
	checking} - procedures must be explicitly typed.  Java
	supports the creation of {virus}-free, tamper-free systems
	with {authentication} based on {public-key encryption}.

	Java has an extensive library of routines for all kinds of
	programming tasks, rivalling that of other languages.

	For example, the "java.net} package supports {TCP/IP}
	{protocols} like {HTTP} and {FTP}.  Java applications can
	access objects across the {Internet} via {URLs} almost as easily as
	on the local {file system}. There are also capabilities for
	several types of distributed applications.

	The Java {GUI} libraries provide portable interfaces.  For example,
	there is an abstract Window class and implementations of it
	for {Unix}, {Microsoft Windows} and the {Macintosh}.
	The "java.awt" and "javax.swing" classes can be used either in
	Web-based "Applets" or in client-side or "desktop" applications.

	There are also packages for developing {XML} applications,
	{web services}, {servlets} and other web applications,
	{security}, date and time calculations and I/O formatting,
	database ({JDBC}), and many others.

	Java is not directly related to {JavaScript} despite the name.

	{Home (http://java.sun.com/)}.

	{Usenet} newsgroup: {news:comp.lang.java}.

	(2005-01-21)

<programming> (API, or "application programming interface")
	The interface (calling conventions) by which an {application
	program} accesses {operating system} and other services.  An
	API is defined at {source code} level and provides a level of
	{abstraction} between the application and the {kernel} (or
	other privileged utilities) to ensure the {portability} of the
	code.

	An API can also provide an interface between a {high level
	language} and lower level utilities and services which were
	written without consideration for the {calling conventions}
	supported by compiled languages.  In this case, the API's main
	task may be the translation of parameter lists from one format
	to another and the interpretation of {call-by-value} and
	{call-by-reference} arguments in one or both directions.

	(1995-02-15)

1. The art of debugging a blank sheet of paper (or, in these
	days of on-line editing, the art of debugging an empty file).

	2. A pastime similar to banging one's head against a wall, but
	with fewer opportunities for reward.

	3. The most fun you can have with your clothes on (although
	clothes are not mandatory).

	[{Jargon File}]

	(2003-02-12)

<electronics> The quantity of {charge} per unit time, measured
	in Amperes (Amps, A).  By historical convention, the sign of
	current is positive for currents flowing from positive to
	negative {potential}, but experience indicates that electrons
	are negatively charged and flow in the opposite direction.

	(1995-10-05)

1. See {multithreading}.

	2. See {threaded code}.

	3. {topic thread}.

	[{Jargon File}]

<World-Wide Web> A {Java} program which can be distributed as
	an attachment in a {World-Wide Web} document and executed by a
	Java-enabled {web browser} such as Sun's {HotJava},
	{Netscape Navigator} version 2.0, or {Internet Explorer}.

	Navigator severely restricts the applet's file system and
	network access in order to prevent accidental or deliberate
	security violations.  Full Java applications, which run
	outside of the browser, do not have these restrictions.

	Web browsers can also be extended with {plug-ins} though these
	differ from applets in that they usually require manual
	installation and are {platform}-specific.  Various other
	languages can now be embedded within {HTML} documents, the
	most common being {JavaScript}.

	Despite Java's aim to be a "write once, run anywhere"
	language, the difficulty of accomodating the variety of
	browsers in use on the Internet has led many to abandon
	client-side processing in favour of {server}-side Java
	programs for which the term {servlet} was coined.

	Merriam Webster "Collegiate Edition" gives a 1990 definition:
	a short application program especially for performing a simple
	specific task.

	(2002-07-12)

After-sale handholding; something many software vendors
	promise but few deliver.  To hackers, most support people are
	useless - because by the time a hacker calls support he or she
	will usually know the software and the relevant manuals better
	than the support people (sadly, this is *not* a joke or
	exaggeration).  A hacker's idea of "support" is a tte--tte
	or exchange of {electronic mail} with the software's designer.

	[{Jargon File}]

	(1995-02-15)

<programming> One of a sequence of copies of a program, each
	incorporating new modifications.  Each version is usually
	identified by a number, commonly of the form X.Y where X is
	the major version number and Y is the release number.
	Typically an increment in X (with Y reset to zero) signifies a
	substantial increase in the function of the program or a
	partial or total re-implementation, whereas Y increases each
	time the progam is changed in any way and re-released.

	Version numbers are useful so that the user can know if the
	program has changed ({bugs} have been fixed or new functions
	added) since he obtained his copy and the programmer can tell
	if a bug report relates to the current version.  It is thus
	always important to state the version when reporting bugs.
	Statements about compatibility between different software
	components should always say which versions they apply to.

	See {change management}.

	(1997-12-07)