https://jumplink.eu/en/blog/tags/gnome/feed.xml 2026-10-29T00:00:00Z Pascal Garber https://jumplink.eu/ https://jumplink.eu/en/blog/learn6502/ 2026-10-29T00:00:00Z 2026-10-29T00:00:00Z

Learn 6502 Assembly is a GNOME app with tutorial, editor, debugger and a virtual display, based on Nick Morgan's easy6502.

<p>The 6502 is the processor of the Commodore 64, the NES and the Apple II. Nick Morgan&#39;s <a href="https://github.com/skilldrick/easy6502">easy6502</a> is a web tutorial that teaches its assembly language step by step. I turned it into a native GNOME app: <strong>Learn 6502 Assembly</strong>.</p> <p>What is in it:</p> <ul><li><strong>An interactive tutorial</strong> that walks through the core concepts.</li><li><strong>A code editor</strong> with syntax highlighting.</li><li><strong>An assembler and a debugger</strong> that show registers, flags and memory while the code runs.</li><li><strong>A virtual display</strong> where you see the result, which is what makes small games and graphics possible.</li></ul> <p>It is written in TypeScript with GJS and libadwaita, and built with <a href="https://gjsify.org/">gjsify</a>. The repository holds more than the desktop app: the assembler, simulator and disassembler live in their own package, <code>@learn6502/core</code>, and the same code also drives a web version and an Android app. The tutorial content and the translations are separate packages too, and translating happens on Weblate.</p> <p>The app is on <a href="https://flathub.org/apps/eu.jumplink.Learn6502">Flathub</a>. The code is GPL-3.0; the tutorial text is CC BY 4.0, as in the original.</p> https://jumplink.eu/en/blog/why-gjsify/ 2026-10-28T00:00:00Z 2026-10-28T00:00:00Z

gjsify brings the standard Node.js and web APIs to GJS, so TypeScript apps and npm packages run natively on GNOME.

<p>GNOME apps can be written in JavaScript. The runtime is GJS, powered by SpiderMonkey. But GJS is neither Node.js nor a browser: there is no <code>node:fs</code>, no <code>fetch</code>, no <code>&lt;canvas&gt;</code> and no npm ecosystem waiting for you. Many libraries, whether an HTTP client, a game engine or a crypto library, assume APIs that GJS does not have.</p> <p><a href="https://gjsify.org/">gjsify</a> fills that gap. It reimplements the Node.js, web and DOM APIs on top of GNOME&#39;s own libraries:</p> <table><thead><tr><th>You write</th><th>gjsify runs it on</th></tr></thead><tbody><tr><td><code>node:fs</code>, <code>node:net</code>, <code>node:crypto</code></td><td>Gio, GLib</td></tr><tr><td><code>fetch</code>, <code>WebSocket</code>, <code>XMLHttpRequest</code></td><td>Soup 3</td></tr><tr><td><code>&lt;canvas&gt;</code> 2D and WebGL</td><td>Cairo, Gtk.GLArea</td></tr><tr><td>WebRTC, WebAudio, <code>&lt;video&gt;</code></td><td>GStreamer</td></tr><tr><td><code>node:sqlite</code></td><td>libsqlite3</td></tr></tbody></table> <p>This makes the standard APIs available in GJS. Libraries written for Node.js or the browser now run directly on GJS, with no browser engine and no Node.js runtime. There is no wrapper server, no bundled Chromium and no shelling out to Node. The result is a real GTK 4 and Adwaita app that you can ship as a Flatpak and that still speaks the language of the wider JavaScript world.</p> <h3>And the other way round</h3> <p>If you prefer Node.js or Bun, you can keep using them. For that I built the reverse direction too: the GJS APIs, meaning GTK, Adwaita and everything else GObject Introspection offers, are available under those runtimes as well. So every native API runs on every runtime.</p> <p>And it behaves the same there. Tests make sure of that: the same tests check the Node.js APIs, the web APIs, the GObject Introspection APIs and the GJS runtime APIs on each runtime, and the result has to be exactly the same everywhere. That is why you can switch the runtime during development without touching the code.</p> <p>It opens up other systems as well: with gjsify you can ship GJS apps for macOS and Windows, as an <code>.app</code> and <code>.dmg</code>, or as a program folder and <code>.msi</code>.</p> <h3>What I wanted from it</h3> <ul><li><strong>Native on GNOME first.</strong> GJS is the main target.</li><li><strong>The ecosystem, unmodified.</strong> The test is whether npm packages run as they are. The Excalibur.js game engine, WebTorrent, socket.io, three.js, axios and the Anthropic MCP SDK all run on GJS through gjsify, checked against their own upstream tests.</li><li><strong>One source, several runtimes.</strong> GJS, Node.js, Bun, the browser and NativeScript. Each package says which of them it reaches, and the build picks the right implementation.</li><li><strong>No Node.js required.</strong> Install, build, run, test, publish and the Flatpak step all run on GJS itself.</li></ul> <h3>Why I build my apps this way</h3> <p>I know TypeScript, the web and its tooling well, and I want to write GNOME apps without leaving that. <a href="https://github.com/gjsify/ts-for-gir">ts-for-gir</a> gives me types for GTK and every other introspected library, gjsify gives me the APIs and the toolchain. My own apps, such as <a href="https://jumplink.eu/beifahrer/">Beifahrer</a>, <a href="https://jumplink.eu/steuererklaerung/">Steuererklärung</a> and <a href="https://flathub.org/apps/eu.jumplink.Learn6502">Learn 6502 Assembly</a>, are the first test: if something is missing, I fix it in gjsify instead of working around it in the app.</p> <p>The code is on <a href="https://github.com/gjsify/gjsify">GitHub</a>, the documentation at <a href="https://gjsify.org/gjsify/">gjsify.org</a>.</p>