WebAssembly (wasm) Target Platform - Revision history

Sgothel at 06:17, 11 September 2025

2025-09-11T06:17:45Z

← Older revision		Revision as of 08:17, 11 September 2025
Line 6:		Line 6:
	Since Java Applets are not more supported within browser or by OpenJDK for years,		Since Java Applets are not more supported within browser or by OpenJDK for years,
	it may seems feasible to evaluate the WebAssembly target running within e.g. web browser nowadays.		it may seems feasible to evaluate the WebAssembly target running within e.g. web browser nowadays.

			Since March '25 [https://2025.wasm.io/slides/the-future-of-write-once-run-anywhere-from-java-to-webassembly-wasmio25.pdf Recent GraalVM on JDK25 supports the wasm target].

	An initial evaluation on small C++ projects using the emscripten front-end for LLVM's clang++ to wasm compiler, which supports many ported system libraries like SDL, OpenGL, .. has been undertaken successfully with variable results.		An initial evaluation on small C++ projects using the emscripten front-end for LLVM's clang++ to wasm compiler, which supports many ported system libraries like SDL, OpenGL, .. has been undertaken successfully with variable results.

Sgothel: /* GraalVM */

2025-09-11T06:12:41Z

GraalVM

← Older revision		Revision as of 08:12, 11 September 2025
Line 53:		Line 53:

	== GraalVM ==		== GraalVM ==
	GraalVM ~~experimentally~~ hosts wasm ~~only~~ and ~~is producing a~~ wasm target for the wasm (browser) runtime.		GraalVM on JDK 25 hosts wasm and supports ''wasm target'' for the wasm (browser) runtime.
			* [https://2025.wasm.io/slides/the-future-of-write-once-run-anywhere-from-java-to-webassembly-wasmio25.pdf GraalVM Native Image supporting wasm as a target]
	* [https://www.graalvm.org/latest/reference-manual/wasm/ GraalVM + wasm (WebAssembly runtime in Java)]		* [https://www.graalvm.org/latest/reference-manual/wasm/ GraalVM + wasm (WebAssembly runtime in Java)]
	** with the help of emscripten		** with the help of emscripten
	** [https://www.graalvm.org/22.0/reference-manual/native-image/JNI/ GraalVM + JNI]		** [https://www.graalvm.org/22.0/reference-manual/native-image/JNI/ GraalVM + JNI]
	* [https://2025.wasm.io/slides/the-future-of-write-once-run-anywhere-from-java-to-webassembly-wasmio25.pdf GraalVM Native Image supporting wasm as a target]

	[https://github.com/oracle/graal/issues/3391 Request for enhancement about wasm target in GraalVM].		[https://github.com/oracle/graal/issues/3391 Request for enhancement about wasm target in GraalVM].

Gouessej: /* GraalVM */ support wasm as a target

2025-08-25T07:54:12Z

GraalVM: support wasm as a target

← Older revision		Revision as of 09:54, 25 August 2025
Line 53:		Line 53:

	== GraalVM ==		== GraalVM ==
	GraalVM experimentally hosts wasm only,		GraalVM experimentally hosts wasm only and is producing a wasm target for the wasm (browser) runtime.
	~~but~~ is ~~not~~ producing a wasm target for the wasm (browser) runtime.		* [https://www.graalvm.org/latest/reference-manual/wasm/ GraalVM + wasm (WebAssembly runtime in Java)]
	* [https://www.graalvm.org/latest/reference-manual/wasm/ GraalVM + wasm]
	** with the help of emscripten		** with the help of emscripten
	** [https://www.graalvm.org/22.0/reference-manual/native-image/JNI/ GraalVM + JNI]		** [https://www.graalvm.org/22.0/reference-manual/native-image/JNI/ GraalVM + JNI]
			* [https://2025.wasm.io/slides/the-future-of-write-once-run-anywhere-from-java-to-webassembly-wasmio25.pdf GraalVM Native Image supporting wasm as a target]

	[https://github.com/oracle/graal/issues/3391 Request for enhancement about wasm target in GraalVM].		[https://github.com/oracle/graal/issues/3391 Request for enhancement about wasm target in GraalVM].

Sgothel at 20:50, 27 May 2025

2025-05-27T20:50:54Z

← Older revision		Revision as of 22:50, 27 May 2025
Line 8:		Line 8:

	An initial evaluation on small C++ projects using the emscripten front-end for LLVM's clang++ to wasm compiler, which supports many ported system libraries like SDL, OpenGL, .. has been undertaken successfully with variable results.		An initial evaluation on small C++ projects using the emscripten front-end for LLVM's clang++ to wasm compiler, which supports many ported system libraries like SDL, OpenGL, .. has been undertaken successfully with variable results.
			* [https://webassembly.org/ WebAssembly]
			* [https://emscripten.org/ emscripten]
	* [https://jausoft.com/cgit/cs_class/gfxbox2.git/about/ gfxbox2 C++/wasm evaluation]		* [https://jausoft.com/cgit/cs_class/gfxbox2.git/about/ gfxbox2 C++/wasm evaluation]
	* [https://~~emscripten~~.~~org~~/ ~~emscripten]~~		* Project [https://jausoft.com/cgit/gamp.git/about/ Gamp]
	* [https://~~webassembly.org~~/ ~~WebAssembly~~]

	The wasm target is comparable to Java bytecode but the wasm virtual machine is not as performant, efficient or flexible as actual native code. The lack of hassle free native threads and native high-performance may remind one of the first JVM steps. The wasm code runs within a virtual machine like the JVM and additionally lacks of native binding capabilities.		The wasm target is comparable to Java bytecode but the wasm virtual machine is not as performant, efficient or flexible as actual native code. The lack of hassle free native threads and native high-performance may remind one of the first JVM steps. The wasm code runs within a virtual machine like the JVM and additionally lacks of native binding capabilities.
Line 24:		Line 25:

	The underlying LLVM compiler did an excellent job and overall, the transition was easy and almost involved no code changes but dropping native thread (std::thread) usage.		The underlying LLVM compiler did an excellent job and overall, the transition was easy and almost involved no code changes but dropping native thread (std::thread) usage.

	'''Project [https://jausoft.com/cgit/gamp.git/about/ Gamp]''' has been created to address Graph and GraphUI, implemented in C++ to be utilized natively and [https://jausoft.com/cgit/gamp.git/about/#online-webassembly-examples within a browser] via WebAssembly.

	The overall program structure had to be adapted to align to the single-thread main-loop workflow		The overall program structure had to be adapted to align to the single-thread main-loop workflow
Line 31:		Line 30:
	All in all, nothing to be too afraid of and depending on the class of applications to be ported		All in all, nothing to be too afraid of and depending on the class of applications to be ported
	to the browser these days, a feasible procedure.		to the browser these days, a feasible procedure.

			= Project [https://jausoft.com/cgit/gamp.git/about/ Gamp] =
			[https://jausoft.com/cgit/gamp.git/about/ Gamp] stands for Graphics, Audio, Multimedia and Processing, the same way as JogAmp, but natively plus using WebAssembly.

			Gamp replicates JogAmp's experience natively via C++ in a condensed form, allowing a similar workflow on native targets and [https://jausoft.com/cgit/gamp.git/about/#online-webassembly-examples within the browser] via WebAssembly. Ironically this will bring back runs everywhere including the web.

			Initial goal reimplementing [https://jausoft.com/blog/tag/graph_type_rendering/ Resolution independent NURBS curves rendering using programmable graphics pipeline (Graph)] has been completed.

			Gamp uses [https://jausoft.com/cgit/jaulib.git/about/ jaulib] for general purpose functionality including linear algebra and geometry and builds upon initial wasm experience collected with [https://jausoft.com/cgit/cs_class/gfxbox2.git/about/ gfxbox2].

	= Java Support =		= Java Support =

Sgothel: /* Initial C++/wasm Evaluation */

2025-05-27T18:11:37Z

Initial C++/wasm Evaluation

← Older revision		Revision as of 20:11, 27 May 2025
Line 19:		Line 19:

	= Initial C++/wasm Evaluation =		= Initial C++/wasm Evaluation =
	[https://jausoft.com/cgit/cs_class/gfxbox2.git/about/ Our little gfxbox2 games] compiled to [https://webassembly.org/ wasm] run about ~~40-60~~% slower within a browser than in native code, depending on coding strategy of our graphics (pixelmap vs SDL/OpenGL primitives).		[https://jausoft.com/cgit/cs_class/gfxbox2.git/about/ Our little gfxbox2 games] compiled to [https://webassembly.org/ wasm] run about ~50% slower [https://jausoft.com/cgit/cs_class/gfxbox2.git/about/#online-webassembly-examples within a browser] than in native code, depending on coding strategy of our graphics (pixelmap vs SDL/OpenGL primitives).

	The used [https://emscripten.org/ emscripten] frontend allowed us to use memory-growth, envelop files used in the wasm file, add cheap stack-overflow cockies and nullptr writes and so forth. Utilization of OpenGL ES via SDL2 was a breeze.		The used [https://emscripten.org/ emscripten] frontend allowed us to use memory-growth, envelop files used in the wasm file, add cheap stack-overflow cockies and nullptr writes and so forth. Utilization of OpenGL ES via SDL2 was a breeze.

	The underlying LLVM compiler did an excellent job and overall, the transition was easy and almost involved no code changes but dropping native thread (std::thread) usage.		The underlying LLVM compiler did an excellent job and overall, the transition was easy and almost involved no code changes but dropping native thread (std::thread) usage.

			'''Project [https://jausoft.com/cgit/gamp.git/about/ Gamp]''' has been created to address Graph and GraphUI, implemented in C++ to be utilized natively and [https://jausoft.com/cgit/gamp.git/about/#online-webassembly-examples within a browser] via WebAssembly.

	The overall program structure had to be adapted to align to the single-thread main-loop workflow		The overall program structure had to be adapted to align to the single-thread main-loop workflow

Sgothel: /* Java Support */

2024-04-04T06:35:12Z

Java Support

← Older revision		Revision as of 08:35, 4 April 2024
Line 32:		Line 32:
	= Java Support =		= Java Support =
	Java bytecode compiler to wasm including some ''runtime envelop''		Java bytecode compiler to wasm including some ''runtime envelop''
	* [https://github.com/google/j2cl/blob/master/docs/getting-started-j2wasm.md J2wasm] within [https://github.com/google/j2cl J2CL] emits ~~very~~ naïve Wasm using the text format and it relies on Binaryen toolchain to assemble, link, and optimize		* [https://github.com/google/j2cl/blob/master/docs/getting-started-j2wasm.md J2wasm] within [https://github.com/google/j2cl J2CL] emits naïve Wasm using the text format and it relies on Binaryen toolchain to assemble, link, and optimize
	** [https://www.wingolog.org/pub/epfl-wasm-gc-feb-2024-slides.pdf 2024 Slides]		** [https://www.wingolog.org/pub/epfl-wasm-gc-feb-2024-slides.pdf 2024 Slides]
	* [https://github.com/konsoletyper/teavm TeaVM] [https://teavm.org/docs/intro/overview.html overview]		* [https://github.com/konsoletyper/teavm TeaVM] [https://teavm.org/docs/intro/overview.html overview]

Sgothel: /* Java Support */

2024-04-04T06:29:52Z

Java Support

← Older revision		Revision as of 08:29, 4 April 2024
Line 32:		Line 32:
	= Java Support =		= Java Support =
	Java bytecode compiler to wasm including some ''runtime envelop''		Java bytecode compiler to wasm including some ''runtime envelop''
			* [https://github.com/google/j2cl/blob/master/docs/getting-started-j2wasm.md J2wasm] within [https://github.com/google/j2cl J2CL] emits very naïve Wasm using the text format and it relies on Binaryen toolchain to assemble, link, and optimize
			** [https://www.wingolog.org/pub/epfl-wasm-gc-feb-2024-slides.pdf 2024 Slides]
	* [https://github.com/konsoletyper/teavm TeaVM] [https://teavm.org/docs/intro/overview.html overview]		* [https://github.com/konsoletyper/teavm TeaVM] [https://teavm.org/docs/intro/overview.html overview]
	* [https://github.com/i-net-software/JWebAssembly JWebAssembly] [https://github.com/i-net-software/JWebAssembly/wiki doc]		* [https://github.com/i-net-software/JWebAssembly JWebAssembly] [https://github.com/i-net-software/JWebAssembly/wiki doc]
Line 39:		Line 41:
	* [https://openjdk.org/jeps/457 JEP 457: Class-File API ]		* [https://openjdk.org/jeps/457 JEP 457: Class-File API ]
	* [https://openjdk.org/projects/babylon/articles/linq Babylon]		* [https://openjdk.org/projects/babylon/articles/linq Babylon]
	* [https://github.com/google/j2cl/blob/master/docs/getting-started-j2wasm.md J2wasm] within [https://github.com/google/j2cl J2CL] emits very naïve Wasm using the text format and it relies on Binaryen toolchain to assemble, link, and optimize
	** [https://www.wingolog.org/pub/epfl-wasm-gc-feb-2024-slides.pdf 2024 Slides]

	== GraalVM ==		== GraalVM ==

Sgothel: /* Java Support */

2024-04-04T06:24:28Z

Java Support

← Older revision		Revision as of 08:24, 4 April 2024
Line 39:		Line 39:
	* [https://openjdk.org/jeps/457 JEP 457: Class-File API ]		* [https://openjdk.org/jeps/457 JEP 457: Class-File API ]
	* [https://openjdk.org/projects/babylon/articles/linq Babylon]		* [https://openjdk.org/projects/babylon/articles/linq Babylon]
	* [https://github.com/google/j2cl/blob/master/docs/getting-started-j2wasm.md J2wasm] within [[https://github.com/google/j2cl J2CL] emits very naïve Wasm using the text format and it relies on Binaryen toolchain to assemble, link, and optimize		* [https://github.com/google/j2cl/blob/master/docs/getting-started-j2wasm.md J2wasm] within [https://github.com/google/j2cl J2CL] emits very naïve Wasm using the text format and it relies on Binaryen toolchain to assemble, link, and optimize
	** [https://www.wingolog.org/pub/epfl-wasm-gc-feb-2024-slides.pdf 2024 Slides]		** [https://www.wingolog.org/pub/epfl-wasm-gc-feb-2024-slides.pdf 2024 Slides]

Sgothel at 06:20, 4 April 2024

2024-04-04T06:20:40Z

← Older revision		Revision as of 08:20, 4 April 2024
Line 37:		Line 37:

	Further interesting bits & pieces		Further interesting bits & pieces
	** [https://openjdk.org/jeps/457 JEP 457: Class-File API ]		* [https://openjdk.org/jeps/457 JEP 457: Class-File API ]
	** [https://openjdk.org/projects/babylon/articles/linq Babylon]		* [https://openjdk.org/projects/babylon/articles/linq Babylon]
			* [https://github.com/google/j2cl/blob/master/docs/getting-started-j2wasm.md J2wasm] within [[https://github.com/google/j2cl J2CL] emits very naïve Wasm using the text format and it relies on Binaryen toolchain to assemble, link, and optimize
			** [https://www.wingolog.org/pub/epfl-wasm-gc-feb-2024-slides.pdf 2024 Slides]

			== GraalVM ==
	GraalVM experimentally hosts wasm only,		GraalVM experimentally hosts wasm only,
	but is not producing a wasm target for the wasm (browser) runtime.		but is not producing a wasm target for the wasm (browser) runtime.

	* [https://www.graalvm.org/latest/reference-manual/wasm/ GraalVM + wasm]		* [https://www.graalvm.org/latest/reference-manual/wasm/ GraalVM + wasm]
	** with the help of emscripten		** with the help of emscripten
	** [https://www.graalvm.org/22.0/reference-manual/native-image/JNI/ GraalVM + JNI]		** [https://www.graalvm.org/22.0/reference-manual/native-image/JNI/ GraalVM + JNI]

			[https://github.com/oracle/graal/issues/3391 Request for enhancement about wasm target in GraalVM].

	= Java Browser Outlook =		= Java Browser Outlook =

Sgothel at 06:10, 4 April 2024

2024-04-04T06:10:11Z

← Older revision		Revision as of 08:10, 4 April 2024
Line 1:		Line 1:
	~~= WebAssembly (wasm) Target Platform =~~

	Extracted from [[SW Tracking Report Feature Objectives Overview\|Feature & Objectives]].		Extracted from [[SW Tracking Report Feature Objectives Overview\|Feature & Objectives]].