<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
  xmlns:content="http://purl.org/rss/1.0/modules/content/"
  xmlns:dc="http://purl.org/dc/elements/1.1/"
  xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
  xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>Chaos Computer Club - LixCon 2026 (low quality mp4)</title>
    <link>https://media.ccc.de/c/lixcon2026</link>
    <description> This feed contains all events from lixcon2026 as mp4</description>
    <copyright>see video outro</copyright>
    <lastBuildDate>Sun, 19 Apr 2026 14:36:52 -0000</lastBuildDate>
    <image>
      <url>https://static.media.ccc.de/media/events/lixcon/2026/logo.png</url>
      <title>Chaos Computer Club - LixCon 2026 (low quality mp4)</title>
      <link>https://media.ccc.de/c/lixcon2026</link>
    </image>
    <item>
      <title>Nix and buck2: from enemies to lovers with snowydeer (lixcon2026)</title>
      <link>https://media.ccc.de/v/lixcon-2026-2-nix-and-buck2-from-enemies-to-lovers-with-snowydeer</link>
      <description>Nix does dependencies and distribution well, but has a controlling personality: it wants to build everything in the build graph.
Buck2 delivers fast, user-friendly, and scalable project builds, but has an equally controlling personality and a lacking public dependency ecosystem.
What if their build graphs touched ... and they were both girls?

In this talk, I will demonstrate how we go from Nix to buck2 to Nix then deploy with containers:
* Using Nix for dependencies in buck2
* Using buck2 in the project build: remote caching, fast builds, ~zero evaluation time
* Importing store paths to Lix from buck2 output while correctly handling dependencies
* Extending these techniques to build Docker images defined entirely in buck2, using nixpkgs `dockerTools`

This talk focuses on buck2, but the techniques used apply to any powerful non-Nix build system.

Hermetic build systems are hard to interoperate with, but there are cheat codes: by resolving their trust issues, you can combine their respective benefits.

For the last year, my team and I have been working on a Buck2 migration for one of the largest Haskell codebases in industry to reduce build times from dozens of minutes to seconds and improve user experience.
We use Nix to orchestrate hundreds of Haskell dependencies and hundreds more dependencies across the Rust, TypeScript, Python and C ecosystems.
On top of that, we are running a much newer Haskell compiler than most of the industry due to active involvement in GHC development, which means a *heavily* patched nixpkgs Haskell dependency set to be able to incorporate these improvements.
By building a Nix-Buck2-Nix sandwich, we were able to focus on rewriting our product build in buck2 while keeping both our Nix-based dependencies and our deployment pipelines to both NixOS and AWS ECS completely as-is.

The novel contributions of this talk are:
* Creating full-featured store paths *entirely* outside of Nix with Snowydeer:
  * Reference scanning outside of Nix using ripgrep
  * Using a new Lix CLI feature: output-addressed paths with references
  * Referencing those store paths from Nix language for further processing
* Using Nix as a build step rather than a build driver to create an ergonomic Docker image builder with Snowydeer Container

This talk builds on previous work, such as:
- [&quot;Integrating Nix and Buck2 for fun and profit&quot;](https://www.youtube.com/watch?v=pDkFk7iggIE) by Claudio Bley
- [&quot;Haskell Builds at Scale: Comparing Bazel and Buck2&quot;](https://www.youtube.com/watch?v=eA-3Gfr4epU) by Andreas Herrmann
- [&quot;Towards Dream Haskell Build Experience&quot;](https://www.youtube.com/watch?v=WrdXUYFnRv4) by Ian-Woo Kim

Licensed to the public under http://creativecommons.org/licenses/by/4.0
about this event: https://pretalx.dgnum.eu/lixcon-2026/talk/Z3CRCM/
</description>
      <enclosure url="https://cdn.media.ccc.de/events/lixcon/2026/h264-sd/lixcon2026-2-eng-Nix_and_buck2_from_enemies_to_lovers_with_snowydeer_sd.mp4"
        length="69206016"
        type="video/mp4"/>
      <pubDate>Fri, 17 Apr 2026 14:50:00 +0200</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/lixcon/2026/h264-sd/lixcon2026-2-eng-Nix_and_buck2_from_enemies_to_lovers_with_snowydeer_sd.mp4?1776607563</guid>
      <dc:identifier>9e126251-90f9-5624-86f7-e41befee6d6b</dc:identifier>
      <dc:date>2026-04-17T14:50:00+02:00</dc:date>
      <itunes:author>Jade Lovelace</itunes:author>
      <itunes:explicit>No</itunes:explicit>
      <itunes:keywords>2, 2026, lixcon2026, Amphitheater Dussane, lixcon2026-eng, Day 1</itunes:keywords>
      <itunes:summary>Nix does dependencies and distribution well, but has a controlling personality: it wants to build everything in the build graph.
Buck2 delivers fast, user-friendly, and scalable project builds, but has an equally controlling personality and a lacking public dependency ecosystem.
What if their build graphs touched ... and they were both girls?

In this talk, I will demonstrate how we go from Nix to buck2 to Nix then deploy with containers:
* Using Nix for dependencies in buck2
* Using buck2 in the project build: remote caching, fast builds, ~zero evaluation time
* Importing store paths to Lix from buck2 output while correctly handling dependencies
* Extending these techniques to build Docker images defined entirely in buck2, using nixpkgs `dockerTools`

This talk focuses on buck2, but the techniques used apply to any powerful non-Nix build system.

Hermetic build systems are hard to interoperate with, but there are cheat codes: by resolving their trust issues, you can combine their respective benefits.

For the last year, my team and I have been working on a Buck2 migration for one of the largest Haskell codebases in industry to reduce build times from dozens of minutes to seconds and improve user experience.
We use Nix to orchestrate hundreds of Haskell dependencies and hundreds more dependencies across the Rust, TypeScript, Python and C ecosystems.
On top of that, we are running a much newer Haskell compiler than most of the industry due to active involvement in GHC development, which means a *heavily* patched nixpkgs Haskell dependency set to be able to incorporate these improvements.
By building a Nix-Buck2-Nix sandwich, we were able to focus on rewriting our product build in buck2 while keeping both our Nix-based dependencies and our deployment pipelines to both NixOS and AWS ECS completely as-is.

The novel contributions of this talk are:
* Creating full-featured store paths *entirely* outside of Nix with Snowydeer:
  * Reference scanning outside of Nix using ripgrep
  * Using a new Lix CLI feature: output-addressed paths with references
  * Referencing those store paths from Nix language for further processing
* Using Nix as a build step rather than a build driver to create an ergonomic Docker image builder with Snowydeer Container

This talk builds on previous work, such as:
- [&quot;Integrating Nix and Buck2 for fun and profit&quot;](https://www.youtube.com/watch?v=pDkFk7iggIE) by Claudio Bley
- [&quot;Haskell Builds at Scale: Comparing Bazel and Buck2&quot;](https://www.youtube.com/watch?v=eA-3Gfr4epU) by Andreas Herrmann
- [&quot;Towards Dream Haskell Build Experience&quot;](https://www.youtube.com/watch?v=WrdXUYFnRv4) by Ian-Woo Kim

Licensed to the public under http://creativecommons.org/licenses/by/4.0
about this event: https://pretalx.dgnum.eu/lixcon-2026/talk/Z3CRCM/
</itunes:summary>
      <itunes:duration>00:25:29</itunes:duration>
    </item>
    <item>
      <title>Using Nix without the Nix: a Retrospective on Zilch (lixcon2026)</title>
      <link>https://media.ccc.de/v/lixcon-2026-14-using-nix-without-the-nix-a-retrospective-on-zilch</link>
      <description>It&#39;s been a while since I last talked about Zilch; and now with Lix&#39;s existence, it&#39;s time to take another look; what&#39;s the status of this mysterious project, and what lessons can we learn from it?

Licensed to the public under http://creativecommons.org/licenses/by/4.0
about this event: https://pretalx.dgnum.eu/lixcon-2026/talk/QFSZRU/
</description>
      <enclosure url="https://cdn.media.ccc.de/events/lixcon/2026/h264-sd/lixcon2026-14-eng-Using_Nix_without_the_Nix_a_Retrospective_on_Zilch_sd.mp4"
        length="71303168"
        type="video/mp4"/>
      <pubDate>Fri, 17 Apr 2026 15:20:00 +0200</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/lixcon/2026/h264-sd/lixcon2026-14-eng-Using_Nix_without_the_Nix_a_Retrospective_on_Zilch_sd.mp4?1776607922</guid>
      <dc:identifier>5f27f28d-189d-5fcb-af63-f999f2992a61</dc:identifier>
      <dc:date>2026-04-17T15:20:00+02:00</dc:date>
      <itunes:author>Puck</itunes:author>
      <itunes:explicit>No</itunes:explicit>
      <itunes:keywords>14, 2026, lixcon2026, Amphitheater Dussane, lixcon2026-eng, Day 1</itunes:keywords>
      <itunes:summary>It&#39;s been a while since I last talked about Zilch; and now with Lix&#39;s existence, it&#39;s time to take another look; what&#39;s the status of this mysterious project, and what lessons can we learn from it?

Licensed to the public under http://creativecommons.org/licenses/by/4.0
about this event: https://pretalx.dgnum.eu/lixcon-2026/talk/QFSZRU/
</itunes:summary>
      <itunes:duration>00:24:51</itunes:duration>
    </item>
    <item>
      <title>To sleep in a sea of Tests | Refactoring a testing &quot;framework&quot; from hell (lixcon2026)</title>
      <link>https://media.ccc.de/v/lixcon-2026-1-to-sleep-in-a-sea-of-tests-refactoring-a-testing-framework-from-hell</link>
      <description>Taking a look at the `functional` test suite, pointing out its concepts and flaws to then take a look at its successor `functional2`

Many curses and screams of frustration has the functional test suite brought forth in many - if not all - lix developers. Hence people wanted a successor. 
In this session, we will talk about all the pain, impurities and falkeyness of the functional suite, look at the features and non-features of functional2, and the pain of migrating tests.

Licensed to the public under http://creativecommons.org/licenses/by/4.0
about this event: https://pretalx.dgnum.eu/lixcon-2026/talk/KBFUXL/
</description>
      <enclosure url="https://cdn.media.ccc.de/events/lixcon/2026/h264-sd/lixcon2026-1-eng-To_sleep_in_a_sea_of_Tests_Refactoring_a_testing_framework_from_hell_sd.mp4"
        length="38797312"
        type="video/mp4"/>
      <pubDate>Fri, 17 Apr 2026 14:15:00 +0200</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/lixcon/2026/h264-sd/lixcon2026-1-eng-To_sleep_in_a_sea_of_Tests_Refactoring_a_testing_framework_from_hell_sd.mp4?1776606771</guid>
      <dc:identifier>dafe38a9-1feb-5273-90f2-5fc8ef102b62</dc:identifier>
      <dc:date>2026-04-17T14:15:00+02:00</dc:date>
      <itunes:author>rootile</itunes:author>
      <itunes:explicit>No</itunes:explicit>
      <itunes:keywords>1, 2026, lixcon2026, Amphitheater Dussane, lixcon2026-eng, Day 1</itunes:keywords>
      <itunes:summary>Taking a look at the `functional` test suite, pointing out its concepts and flaws to then take a look at its successor `functional2`

Many curses and screams of frustration has the functional test suite brought forth in many - if not all - lix developers. Hence people wanted a successor. 
In this session, we will talk about all the pain, impurities and falkeyness of the functional suite, look at the features and non-features of functional2, and the pain of migrating tests.

Licensed to the public under http://creativecommons.org/licenses/by/4.0
about this event: https://pretalx.dgnum.eu/lixcon-2026/talk/KBFUXL/
</itunes:summary>
      <itunes:duration>00:16:59</itunes:duration>
    </item>
    <item>
      <title>Regiux: prototyping a fast Nix interpreter (lixcon2026)</title>
      <link>https://media.ccc.de/v/lixcon-2026-4-regiux-prototyping-a-fast-nix-interpreter</link>
      <description>The Nix expression language is challenging to evaluate due to non-strict semantics, dynamic scoping, a diverse collection of builtin operators, and tight integration with the Nix store. We give a progress report on Regiux, an interpreter for Nix which is narrowly focused on efficient evaluation of expressions.

Regiux is yet another attempt at a fast Nix evaluator. Come learn about the ingredients that go into modern compilers and interpreters, particularly:

* Lexing and parsing
* Desugaring and expanding
* Intermediate languages for lambda calculus
* Using the RPython JIT toolkit
* Bytecode for lazy graph evaluation

Licensed to the public under http://creativecommons.org/licenses/by/4.0
about this event: https://pretalx.dgnum.eu/lixcon-2026/talk/F83VYV/
</description>
      <enclosure url="https://cdn.media.ccc.de/events/lixcon/2026/h264-sd/lixcon2026-4-eng-Regiux_prototyping_a_fast_Nix_interpreter_sd.mp4"
        length="92274688"
        type="video/mp4"/>
      <pubDate>Fri, 17 Apr 2026 11:45:00 +0200</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/lixcon/2026/h264-sd/lixcon2026-4-eng-Regiux_prototyping_a_fast_Nix_interpreter_sd.mp4?1776605685</guid>
      <dc:identifier>96146e73-9f8c-5b23-9a33-e22dedae57ea</dc:identifier>
      <dc:date>2026-04-17T11:45:00+02:00</dc:date>
      <itunes:author>Corbin</itunes:author>
      <itunes:explicit>No</itunes:explicit>
      <itunes:keywords>4, 2026, lixcon2026, Amphitheater Dussane, lixcon2026-eng, Day 1</itunes:keywords>
      <itunes:summary>The Nix expression language is challenging to evaluate due to non-strict semantics, dynamic scoping, a diverse collection of builtin operators, and tight integration with the Nix store. We give a progress report on Regiux, an interpreter for Nix which is narrowly focused on efficient evaluation of expressions.

Regiux is yet another attempt at a fast Nix evaluator. Come learn about the ingredients that go into modern compilers and interpreters, particularly:

* Lexing and parsing
* Desugaring and expanding
* Intermediate languages for lambda calculus
* Using the RPython JIT toolkit
* Bytecode for lazy graph evaluation

Licensed to the public under http://creativecommons.org/licenses/by/4.0
about this event: https://pretalx.dgnum.eu/lixcon-2026/talk/F83VYV/
</itunes:summary>
      <itunes:duration>00:30:51</itunes:duration>
    </item>
    <item>
      <title>The politics of language design (lixcon2026)</title>
      <link>https://media.ccc.de/v/lixcon-2026-3-the-politics-of-language-design</link>
      <description>This talk is about Elpe, a mixture of ideas from Nix, Docker and Ubuntu/Debian/RHEL, with a strong focus on performance and security.

I&#39;ll talk about the design choices I&#39;ve made, and demo the thing and about how choices that may seem purely technical can have extreme political consequences. I&#39;ll also explain how such choices can have deep and lasting consequences on the dynamics of growing organisations.

Licensed to the public under http://creativecommons.org/licenses/by/4.0
about this event: https://pretalx.dgnum.eu/lixcon-2026/talk/HVZTB9/
</description>
      <enclosure url="https://cdn.media.ccc.de/events/lixcon/2026/h264-sd/lixcon2026-3-eng-The_politics_of_language_design_sd.mp4"
        length="109051904"
        type="video/mp4"/>
      <pubDate>Fri, 17 Apr 2026 11:15:00 +0200</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/lixcon/2026/h264-sd/lixcon2026-3-eng-The_politics_of_language_design_sd.mp4?1776605404</guid>
      <dc:identifier>d92f0715-b3ef-513e-b188-0f392ec59017</dc:identifier>
      <dc:date>2026-04-17T11:15:00+02:00</dc:date>
      <itunes:author>Pierre-Étienne Meunier</itunes:author>
      <itunes:explicit>No</itunes:explicit>
      <itunes:keywords>3, 2026, lixcon2026, Amphitheater Dussane, lixcon2026-eng, Day 1</itunes:keywords>
      <itunes:summary>This talk is about Elpe, a mixture of ideas from Nix, Docker and Ubuntu/Debian/RHEL, with a strong focus on performance and security.

I&#39;ll talk about the design choices I&#39;ve made, and demo the thing and about how choices that may seem purely technical can have extreme political consequences. I&#39;ll also explain how such choices can have deep and lasting consequences on the dynamics of growing organisations.

Licensed to the public under http://creativecommons.org/licenses/by/4.0
about this event: https://pretalx.dgnum.eu/lixcon-2026/talk/HVZTB9/
</itunes:summary>
      <itunes:duration>00:38:06</itunes:duration>
    </item>
    <item>
      <title>The untapped potential of Lix plugins (lixcon2026)</title>
      <link>https://media.ccc.de/v/lixcon-2026-13-the-untapped-potential-of-lix-plugins</link>
      <description>Lix plugins — a feature so esoteric none yet remember their existence. What power could they hold? What secrets could they unlock? Let&#39;s discover together!

Licensed to the public under http://creativecommons.org/licenses/by/4.0
about this event: https://pretalx.dgnum.eu/lixcon-2026/talk/PEDV9S/
</description>
      <enclosure url="https://cdn.media.ccc.de/events/lixcon/2026/h264-sd/lixcon2026-13-eng-The_untapped_potential_of_Lix_plugins_sd.mp4"
        length="58720256"
        type="video/mp4"/>
      <pubDate>Fri, 17 Apr 2026 10:45:00 +0200</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/lixcon/2026/h264-sd/lixcon2026-13-eng-The_untapped_potential_of_Lix_plugins_sd.mp4?1776604679</guid>
      <dc:identifier>4f093efc-1c60-5d96-a861-e3f77747b156</dc:identifier>
      <dc:date>2026-04-17T10:45:00+02:00</dc:date>
      <itunes:author>Qyriad</itunes:author>
      <itunes:explicit>No</itunes:explicit>
      <itunes:keywords>13, 2026, lixcon2026, Amphitheater Dussane, lixcon2026-eng, Day 1</itunes:keywords>
      <itunes:summary>Lix plugins — a feature so esoteric none yet remember their existence. What power could they hold? What secrets could they unlock? Let&#39;s discover together!

Licensed to the public under http://creativecommons.org/licenses/by/4.0
about this event: https://pretalx.dgnum.eu/lixcon-2026/talk/PEDV9S/
</itunes:summary>
      <itunes:duration>00:21:14</itunes:duration>
    </item>
    <item>
      <title>Botanix: A Nix native CI in a forge-agnostic world (lixcon2026)</title>
      <link>https://media.ccc.de/v/lixcon-2026-8-botanix-a-nix-native-ci-in-a-forge-agnostic-world</link>
      <description>Botanix is a new CI software that targets a native nix integration as it builds derivations as its pipeline. It integrates natively with both Gerrit and Forgejo currently but its genericity allows for even more diversity in the future!

This talk will present the genesis of the Botanix project, worked on by students from ENS de Lyon, its philosophy and inner workings.

Licensed to the public under http://creativecommons.org/licenses/by/4.0
about this event: https://pretalx.dgnum.eu/lixcon-2026/talk/YZZKYT/
</description>
      <enclosure url="https://cdn.media.ccc.de/events/lixcon/2026/h264-sd/lixcon2026-8-eng-Botanix_A_Nix_native_CI_in_a_forge-agnostic_world_sd.mp4"
        length="37748736"
        type="video/mp4"/>
      <pubDate>Fri, 17 Apr 2026 10:15:00 +0200</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/lixcon/2026/h264-sd/lixcon2026-8-eng-Botanix_A_Nix_native_CI_in_a_forge-agnostic_world_sd.mp4?1776603115</guid>
      <dc:identifier>238ae78e-b9c5-5e6a-98e7-8412f3137205</dc:identifier>
      <dc:date>2026-04-17T10:15:00+02:00</dc:date>
      <itunes:author>Tom Hubrecht</itunes:author>
      <itunes:explicit>No</itunes:explicit>
      <itunes:keywords>8, 2026, lixcon2026, Amphitheater Dussane, lixcon2026-eng, Day 1</itunes:keywords>
      <itunes:summary>Botanix is a new CI software that targets a native nix integration as it builds derivations as its pipeline. It integrates natively with both Gerrit and Forgejo currently but its genericity allows for even more diversity in the future!

This talk will present the genesis of the Botanix project, worked on by students from ENS de Lyon, its philosophy and inner workings.

Licensed to the public under http://creativecommons.org/licenses/by/4.0
about this event: https://pretalx.dgnum.eu/lixcon-2026/talk/YZZKYT/
</itunes:summary>
      <itunes:duration>00:16:41</itunes:duration>
    </item>
    <item>
      <title>Introduction to LixCon (lixcon2026)</title>
      <link>https://media.ccc.de/v/lixcon-2026-9-introduction-to-lixcon</link>
      <description>Welcome to LixCon!

Licensed to the public under http://creativecommons.org/licenses/by/4.0
about this event: https://pretalx.dgnum.eu/lixcon-2026/talk/38JNUB/
</description>
      <enclosure url="https://cdn.media.ccc.de/events/lixcon/2026/h264-sd/lixcon2026-9-eng-Introduction_to_LixCon_sd.mp4"
        length="24117248"
        type="video/mp4"/>
      <pubDate>Fri, 17 Apr 2026 10:00:00 +0200</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/lixcon/2026/h264-sd/lixcon2026-9-eng-Introduction_to_LixCon_sd.mp4?1776594606</guid>
      <dc:identifier>378ba267-be86-570c-90c9-3c58132d3721</dc:identifier>
      <dc:date>2026-04-17T10:00:00+02:00</dc:date>
      <itunes:author>Ryan Lahfa (&quot;RaitoBezarius&quot;)</itunes:author>
      <itunes:explicit>No</itunes:explicit>
      <itunes:keywords>9, 2026, lixcon2026, Amphitheater Dussane, lixcon2026-eng, Day 1</itunes:keywords>
      <itunes:summary>Welcome to LixCon!

Licensed to the public under http://creativecommons.org/licenses/by/4.0
about this event: https://pretalx.dgnum.eu/lixcon-2026/talk/38JNUB/
</itunes:summary>
      <itunes:duration>00:07:39</itunes:duration>
    </item>
    <generator>media.ccc.de / RSS 0.3.1</generator>
    <itunes:category text="Technology"/>
    <itunes:image href="https://static.media.ccc.de/media/events/lixcon/2026/logo.png"/>
    <itunes:owner>
      <itunes:name>CCC media team</itunes:name>
      <itunes:email>media@c3voc.de</itunes:email>
    </itunes:owner>
    <itunes:author>CCC media team</itunes:author>
    <itunes:explicit>No</itunes:explicit>
    <itunes:keywords>CCC Congress Hacking Security Netzpolitik</itunes:keywords>
    <itunes:subtitle>A wide variety of video material distributed by the CCC. All content is taken from cdn.media.ccc.de and media.ccc.de</itunes:subtitle>
    <itunes:summary>A wide variety of video material distributed by the Chaos Computer Club. This feed contains all events from lixcon2026 as mp4</itunes:summary>
  </channel>
</rss>