<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Development on Mica Development UG</title><link>https://mica-dev.com/tags/development/</link><description>Recent content in Development on Mica Development UG</description><image><title>Mica Development UG</title><url>https://mica-dev.com/Mica%20Development%20Web.jpeg</url><link>https://mica-dev.com/Mica%20Development%20Web.jpeg</link></image><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 18 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://mica-dev.com/tags/development/index.xml" rel="self" type="application/rss+xml"/><item><title>The Dragon SDK stands alone</title><link>https://mica-dev.com/blog/dragon-sdk-standalone/</link><pubDate>Tue, 18 Aug 2026 00:00:00 +0000</pubDate><guid>https://mica-dev.com/blog/dragon-sdk-standalone/</guid><description>With 7.1 the SDK becomes a complete product of its own: the runtime floor ships as its own package under a licence written for toolchains, your emitted programs link no Mica standard library, and a compiler you build on Dragon installs and works without the Mica compiler anywhere on the machine.</description></item><item><title>The Dragon SDK: our backend, as a deliverable</title><link>https://mica-dev.com/blog/dragon-sdk/</link><pubDate>Wed, 05 Aug 2026 00:00:00 +0000</pubDate><guid>https://mica-dev.com/blog/dragon-sdk/</guid><description>The engine that compiles Mica — control-flow analysis, SSA middle-end, storage placement, register allocation, native emission — is now something you can build a compiler against. Here is what it is, why we published it, and where it goes.</description></item><item><title>The breakup: one compiler becomes four modules — and gains a second language</title><link>https://mica-dev.com/blog/the-breakup/</link><pubDate>Sat, 01 Aug 2026 00:00:00 +0000</pubDate><guid>https://mica-dev.com/blog/the-breakup/</guid><description>After three years as one program, the Mica compiler now has the architecture it always claimed to have: a foundation, an intermediate language, a backend engine, and a frontend — with walls between them a build system enforces. The proof is a second language: Wirth&amp;#39;s PL/0, compiled to native code by Mica&amp;#39;s own backend, checked against Wirth&amp;#39;s own machine.</description></item><item><title>Mica gets a project model</title><link>https://mica-dev.com/blog/project-model/</link><pubDate>Tue, 28 Jul 2026 00:00:00 +0000</pubDate><guid>https://mica-dev.com/blog/project-model/</guid><description>A three-line mica.project beside your sources tells the compiler and the editor the same truth: which files form the program, which encoding they speak, and which libraries they consume — and one program can now import several separately built libraries.</description></item><item><title>Run a Mica file like a script</title><link>https://mica-dev.com/blog/run-flag/</link><pubDate>Tue, 28 Jul 2026 00:00:00 +0000</pubDate><guid>https://mica-dev.com/blog/run-flag/</guid><description>mica --run compiles and executes one source file in a single command — millisecond compiles, full checks, argv and exit codes the way a shell expects them, shebang support, and automatic use of your project&amp;#39;s libraries. Compiled-language speed with scripting-language ease.</description></item><item><title>The 6.12.5 preview: projects and scripting</title><link>https://mica-dev.com/blog/release-6-12-5-preview/</link><pubDate>Tue, 28 Jul 2026 00:00:00 +0000</pubDate><guid>https://mica-dev.com/blog/release-6-12-5-preview/</guid><description>The preview of 6.12.5, which carried two features that belong together: the project file the compiler and the editor both read, and the run mode that makes one Mica file as easy to run as a script. Both have since shipped.</description></item></channel></rss>