<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>WebAssembly on webtechie.be</title>
		<link>https://webtechie.be/tags/webassembly/</link>
		<description>Recent content in WebAssembly on webtechie.be</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Mon, 15 Jun 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://webtechie.be/tags/webassembly/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Foojay Podcast #98: The End of JNI Pain, How WebAssembly Is Quietly Replacing Native Libraries in Java</title>
				<link>https://webtechie.be/podcasts/2026/2026-06-15-foojay-podcast-98-webassembly-jni-chicory/</link>
				<pubDate>Mon, 15 Jun 2026 00:00:00 +0000</pubDate>
				<guid>https://webtechie.be/podcasts/2026/2026-06-15-foojay-podcast-98-webassembly-jni-chicory/</guid>
				<description>&lt;p&gt;JNI has been the standard answer for calling native code from Java for almost three decades. It also brings most of the headaches anyone who has wrestled with it remembers: brittle bindings, crashes that take the JVM down with them, painful cross-platform builds. WebAssembly quietly changes the shape of that problem. You get a sandboxed runtime, a portable binary format, and a far gentler integration path into the JVM.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
