From days of old...

Invoking Applet Methods From JavaScript Code - https://docs.oracle.com/javase/tutorial/deployment/applet/in...

and

Invoking JavaScript Code From an Applet - https://docs.oracle.com/javase/tutorial/deployment/applet/in...

Aside from the "Java is cool, name everything Java" in the early days - there was scripting between the browser and the applet using a language named JavaScript.

▲

bartread 4 hours ago | parent | next [-]

I actually used this back in the day: once at university, and then again for a telecoms project in my first job.

But it doesn't mean there's much commonality - beyond superficially C-like syntax - between the languages, and certainly not between their "standard libraries" (aka the browser APIs in JavaScript's case).

▲

zdragnar 5 hours ago | parent | prev [-]

Eh, JavaScript wasn't the originally chosen name, it was LiveScript by Eich. I've never seen a justification for the name from anyone in the know, other than Eich's musing that Netscape wanted the "cool" factor. That "cool" factor was also why the original task of embedding scheme into the browser turned into a more C/Java-esque flavor.

	▲	shagie 3 hours ago \| parent \| next [-]
		> Java applets can invoke JavaScript functions present in the same web page as the applet. The LiveConnect Specification describes details about how JavaScript code communicates with Java code. https://docs.oracle.com/javase/tutorial/deployment/applet/in... > LiveConnect is a feature of web browsers which allows Java applets to communicate with the JavaScript engine in the browser, and JavaScript on the web page to interact with applets. The LiveConnect concept originated in the Netscape web browser, and to this date, Mozilla and Firefox browsers have had the most complete support for LiveConnect features. It has, however, been possible to call between JavaScript and Java in some fashion on all web browsers for a number of years. https://www.oracle.com/java/technologies/javase/liveconnect-... -- The naming appears to be confused. https://web.archive.org/web/20101115234856/http://www.oracle... > Improved Java/JavaScript communication. The bridge between the JavaScript engine in the web browser and the Java programming language has been completely reimplemented. The new implementation is backward-compatible and features improved reliability, performance and cross-browser portability, for both Java calling JavaScript as well as JavaScript calling Java. Formerly Mozilla-specific "LiveConnect" functionality, such as the ability to call static Java methods, instantiate new Java objects and reference third-party packages from JavaScript, is now available in all browsers. The "LiveConnect" relating to the original LiveScript maybe? And that LiveConnect was a Netscape/Mozilla driven thing. My point was more one of "JavaScript was the glue between applets and the HTML page itself early in the development of the language." Renaming LiveScript to JavaScript and promoting the LiveConnect functionality wasn't an unreasonable thing at the time.
	▲	chuckadams 4 hours ago \| parent \| prev [-]
		Sun was pushing it as a way to script Java applets. Might have even worked out if LiveConnect (the interface layer between Java and JS) wasn't such buggy trash.