Lobsters Digest (AI)

lobsters-digest.xml

<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Lobsters Digest</title>
    <link>https://lobste.rs</link>
    <atom:link href="https://gist.githubusercontent.com/puf/0acff45b98d3eacd2bf56566884c90cc/raw/lobsters-digest.xml" rel="self" type="application/rss+xml" />
    <description>AI-summarized updates from Lobsters.</description>
    <lastBuildDate>Fri, 13 Feb 2026 13:10:00 -0800</lastBuildDate>
    <item>
      <title>Evolving Git for the next decade</title>
      <link>https://lwn.net/SubscriberLink/1057561/bddc1e61152fadf6/</link>
      <description><![CDATA[<p><strong>The Gist:</strong> A deep dive into Git's evolution as it turns 20. Key shifts include the slow transition from SHA-1 to SHA-256 (stalled by ecosystem support), the move to "reftables" (a binary backend for references) to handle massive monorepos, and better large file support via "large-object promisors." The author also notes UI improvements inspired by the `Jujutsu` VCS, such as easier history splitting and treating commits as malleable drafts.</p>
<p><strong>The Lobsters Take:</strong> Discussion highlights that better large file handling is critical, especially for game devs and AI model versioning. Users suggest content-defined chunking (like `git-xet`) is the standard solution Git should adopt.</p>
<p><a href="https://lobste.rs/s/jcio2j/evolving_git_for_next_decade">Comments on Lobsters</a></p>]]></description>
      <pubDate>Fri, 13 Feb 2026 12:09:21 -0600</pubDate>
      <guid>https://lobste.rs/s/jcio2j</guid>
      <comments>https://lobste.rs/s/jcio2j/evolving_git_for_next_decade</comments>
    </item>
    <item>
      <title>moss-kernel: Rust Linux-compatible kernel</title>
      <link>https://github.com/hexagonal-sun/moss-kernel</link>
      <description><![CDATA[<p><strong>The Gist:</strong> Moss is an experimental Unix-like kernel written in Rust and Aarch64 assembly. It features an asynchronous core (using Rust's async/await), a modular architecture, and binary compatibility with Linux userspace (capable of running Arch Linux binaries). It currently implements ~105 syscalls and aims to explore safe, async kernel design.</p>
<p><strong>The Lobsters Take:</strong> One user noted the similarity to other recent Rust-based Linux-compatible kernel projects.</p>
<p><a href="https://lobste.rs/s/9ltmes/moss_kernel_rust_linux_compatible_kernel">Comments on Lobsters</a></p>]]></description>
      <pubDate>Fri, 13 Feb 2026 08:13:23 -0600</pubDate>
      <guid>https://lobste.rs/s/9ltmes</guid>
      <comments>https://lobste.rs/s/9ltmes/moss_kernel_rust_linux_compatible_kernel</comments>
    </item>
    <item>
      <title>I Improved 15 LLMs at Coding in One Afternoon</title>
      <link>https://blog.can.ac/2026/02/12/the-harness-problem/</link>
      <description><![CDATA[<p><strong>The Gist:</strong> The author demonstrates that the "harness" (specifically the edit format) is a major bottleneck for AI coding agents. By switching from `apply_patch` or `str_replace` to "Hashline" (tagging every line with a short hash for stable references), they achieved significant performance boosts (e.g., +8% for Gemini) and reduced token usage. The post also mentions the author being banned by Google for benchmarking and Anthropic blocking OpenCode.</p>
<p><strong>The Lobsters Take:</strong> Users find the "Hashline" concept intriguing but worry about the "strangeness tax"—increased token usage for the model to understand the custom format—and whether it scales to whole-conversation contexts.</p>
<p><a href="https://lobste.rs/s/pc7u1q/i_improved_15_llms_at_coding_one_afternoon">Comments on Lobsters</a></p>]]></description>
      <pubDate>Thu, 12 Feb 2026 21:36:49 -0600</pubDate>
      <guid>https://lobste.rs/s/pc7u1q</guid>
      <comments>https://lobste.rs/s/pc7u1q/i_improved_15_llms_at_coding_one_afternoon</comments>
    </item>
    <item>
      <title>A Deep Dive into Apple's .car File Format</title>
      <link>https://dbg.re/posts/car-file-format/</link>
      <description><![CDATA[<p><strong>The Gist:</strong> A reverse engineering deep dive into Apple's Compiled Asset Record (.car) format. The author explains it relies on the BOMStore (Bill of Materials) format and B+ trees to map asset keys to Core Structured Image (CSI) blocks. The post details the compression methods (LZFSE, RLE), pixel formats, and metadata structures, and includes an interactive WebAssembly parser.</p>
<p><strong>The Lobsters Take:</strong> <a href="https://lobste.rs/c/gcxb5z">classichasclass</a> praises the detective work but notes a preference for command-line tools over browser-based WebAssembly demos.</p>
<p><a href="https://lobste.rs/s/z6myes/deep_dive_into_apple_s_car_file_format">Comments on Lobsters</a></p>]]></description>
      <pubDate>Fri, 13 Feb 2026 10:28:07 -0600</pubDate>
      <guid>https://lobste.rs/s/z6myes</guid>
      <comments>https://lobste.rs/s/z6myes/deep_dive_into_apple_s_car_file_format</comments>
    </item>
    <item>
      <title>microgpt</title>
      <link>http://karpathy.github.io/2026/02/12/microgpt/</link>
      <description><![CDATA[<p><strong>The Gist:</strong> Andrej Karpathy released `microgpt`, a 200-line pure Python implementation (zero dependencies) of a GPT model. It includes the dataset loader, tokenizer, autograd engine, transformer architecture, and training loop. The project aims to demonstrate the "algorithmic essence" of LLMs without the complexity of production engineering (GPUs, batching, etc.).</p>
<p><strong>The Lobsters Take:</strong> No comments yet.</p>
<p><a href="https://lobste.rs/s/uyjjtz/microgpt">Comments on Lobsters</a></p>]]></description>
      <pubDate>Fri, 13 Feb 2026 10:08:13 -0600</pubDate>
      <guid>https://lobste.rs/s/uyjjtz</guid>
      <comments>https://lobste.rs/s/uyjjtz/microgpt</comments>
    </item>
    <item>
      <title>The 12-Factor App - 15 Years later. Does it Still Hold Up in 2026?</title>
      <link>https://lukasniessen.medium.com/the-12-factor-app-15-years-later-does-it-still-hold-up-in-2026-c8af494e8465</link>
      <description><![CDATA[<p><strong>The Gist:</strong> A review of the 12-Factor App methodology 15 years post-launch. The author argues most factors remain highly relevant (Codebase, Dependencies, Config, Backing Services), while others have evolved (Logs are now part of Observability/OpenTelemetry; Port Binding is less applicable to serverless). A 13th factor is proposed: Forward and Backward Compatibility to support zero-downtime deployments.</p>
<p><strong>The Lobsters Take:</strong> One commenter agrees "absolutely, yes" with the analysis and suggests adding that database schema upgrades should be handled out-of-band to prevent simultaneous upgrade conflicts during rollouts.</p>
<p><a href="https://lobste.rs/s/t7jbfe/12_factor_app_15_years_later_does_it_still">Comments on Lobsters</a></p>]]></description>
      <pubDate>Fri, 13 Feb 2026 09:36:54 -0600</pubDate>
      <guid>https://lobste.rs/s/t7jbfe</guid>
      <comments>https://lobste.rs/s/t7jbfe/12_factor_app_15_years_later_does_it_still</comments>
    </item>
    <item>
      <title>Thanks for All the Frames: Rust GUI Observations</title>
      <link>https://tritium.legal/blog/desktop</link>
      <description><![CDATA[<p><strong>The Gist:</strong> The Tritium team (building a legal word processor) attempted to migrate their UI from `egui` (immediate mode) to `slint` (retained mode) for better power efficiency and OS integration. They abandoned the effort after 4 weeks because `slint` (like other Rust GUIs) relies on `winit`, which has critical bugs on macOS regarding file association/delegation. They decided to stick with `egui` and patch around the issues.</p>
<p><strong>The Lobsters Take:</strong> No comments yet.</p>
<p><a href="https://lobste.rs/s/misukt/thanks_for_all_frames_rust_gui">Comments on Lobsters</a></p>]]></description>
      <pubDate>Fri, 13 Feb 2026 09:21:06 -0600</pubDate>
      <guid>https://lobste.rs/s/misukt</guid>
      <comments>https://lobste.rs/s/misukt/thanks_for_all_frames_rust_gui</comments>
    </item>
    <item>
      <title>Resizing windows on macOS Tahoe – the saga continues</title>
      <link>https://noheger.at/blog/2026/02/12/resizing-windows-on-macos-tahoe-the-saga-continues/</link>
      <description><![CDATA[<p><strong>The Gist:</strong> A follow-up on macOS window resizing usability. While the macOS 26.3 RC appeared to fix the issue by using rounded corner hit-testing, the final release reverted to square regions and a thin (6px) resize zone, making it difficult to grab window edges.</p>
<p><strong>The Lobsters Take:</strong> <a href="https://lobste.rs/c/pdcnou">classichasclass</a> expresses confusion over the provided images, finding it difficult to distinguish the resize zone behavior between versions.</p>
<p><a href="https://lobste.rs/s/kegsv1/resizing_windows_on_macos_tahoe_saga">Comments on Lobsters</a></p>]]></description>
      <pubDate>Fri, 13 Feb 2026 09:09:58 -0600</pubDate>
      <guid>https://lobste.rs/s/kegsv1</guid>
      <comments>https://lobste.rs/s/kegsv1/resizing_windows_on_macos_tahoe_saga</comments>
    </item>
    <item>
      <title>Hare 0.26.0 released</title>
      <link>https://harelang.org/blog/2026-02-13-hare-0.26.0-released/</link>
      <description><![CDATA[<p><strong>The Gist:</strong> Hare 0.26.0 has been released. Key features include `for..else` loops (allowing loops to return values), support for DragonflyBSD, explicit error ignoring with `_`, and the ability to declare uninitialized variables with `@undefined`. This is a stable release following version 0.25.2.</p>
<p><strong>The Lobsters Take:</strong> One user shares they enjoyed working with Hare previously but wonders if Linear types (or similar resource management constructs) will be added in the future.</p>
<p><a href="https://lobste.rs/s/wqzxyu/hare_0_26_0_released">Comments on Lobsters</a></p>]]></description>
      <pubDate>Fri, 13 Feb 2026 07:14:23 -0600</pubDate>
      <guid>https://lobste.rs/s/wqzxyu</guid>
      <comments>https://lobste.rs/s/wqzxyu/hare_0_26_0_released</comments>
    </item>
    <item>
      <title>What are you doing this weekend?</title>
      <link>https://lobste.rs/s/mclhjq/what_are_you_doing_this_weekend</link>
      <description><![CDATA[<p><strong>The Gist:</strong> The weekly community thread for sharing weekend plans. The OP shares their own project: rewriting a Zig WireGuard implementation to better adhere to specs, alongside cooking plans involving beef wellington and fermented tomato ragu.</p>
<p><strong>The Lobsters Take:</strong> No comments yet.</p>
<p><a href="https://lobste.rs/s/mclhjq/what_are_you_doing_this_weekend">Comments on Lobsters</a></p>]]></description>
      <pubDate>Fri, 13 Feb 2026 03:15:45 -0600</pubDate>
      <guid>https://lobste.rs/s/mclhjq</guid>
      <comments>https://lobste.rs/s/mclhjq/what_are_you_doing_this_weekend</comments>
    </item>
    <item>
      <title>Google might think your Website is down</title>
      <link>https://codeinput.com/blog/google-seo</link>
      <description><![CDATA[<p><strong>The Gist:</strong> The author discovered that Google's AI Overview incorrectly flagged their site as "offline" in early 2026. This happened because the AI crawled a status popup component (meant to show the status of *other* services) and misinterpreted it as the website's own availability. The post warns that AI aggregators can easily mistake UI elements or user content for authoritative facts.</p>
<p><strong>The Lobsters Take:</strong> <a href="https://lobste.rs/c/wivq9a">bediger4000</a> argues this demonstrates that LLMs lack intelligence, as they syntactically process text without understanding context—treating a status indicator as a site-wide declaration.</p>
<p><a href="https://lobste.rs/s/hkrawz/google_might_think_your_website_is_down">Comments on Lobsters</a></p>]]></description>
      <pubDate>Thu, 12 Feb 2026 23:17:21 -0600</pubDate>
      <guid>https://lobste.rs/s/hkrawz</guid>
      <comments>https://lobste.rs/s/hkrawz/google_might_think_your_website_is_down</comments>
    </item>
    <item>
      <title>The Many Flavors of Ignore Files</title>
      <link>https://nesbitt.io/2026/02/12/the-many-flavors-of-ignore-files.html</link>
      <description><![CDATA[<p><strong>The Gist:</strong> The author delves into the intricate nature of `.gitignore` and similar ignore files, highlighting the four layers of patterns in Git and the specific rules for anchors, wildcards, and negation. The article points out that many tools claim to use "gitignore syntax" but often implement only subsets or variations (e.g., Docker, npm). The author suggests the creation of a formal specification or a "CommonIgnore" standard to harmonize behavior, akin to CommonMark for Markdown.</p>
<p><strong>The Lobsters Take:</strong> No comments yet.</p>
<p><a href="https://lobste.rs/s/x3vd7h/many_flavors_ignore_files">Comments on Lobsters</a></p>]]></description>
      <pubDate>Thu, 12 Feb 2026 21:03:33 -0600</pubDate>
      <guid>https://lobste.rs/s/x3vd7h</guid>
      <comments>https://lobste.rs/s/x3vd7h/many_flavors_ignore_files</comments>
    </item>
    <item>
      <title>Apple has a transparency issue</title>
      <link>https://www.youtube.com/watch?v=ejPqAJ0dHwY</link>
      <description><![CDATA[<p><strong>The Gist:</strong> This item is a YouTube video titled "Apple has a transparency issue," implying a critical discussion about Apple's practices regarding transparency.</p>
<p><strong>The Lobsters Take:</strong> No comments yet.</p>
<p><a href="https://lobste.rs/s/bsprvp/apple_has_transparency_issue">Comments on Lobsters</a></p>]]></description>
      <pubDate>Thu, 12 Feb 2026 17:19:34 -0600</pubDate>
      <guid>https://lobste.rs/s/bsprvp</guid>
      <comments>https://lobste.rs/s/bsprvp/apple_has_transparency_issue</comments>
    </item>
    <item>
      <title>.plan files (2020)</title>
      <link>https://matteolandi.net/plan-files.html</link>
      <description><![CDATA[<p><strong>The Gist:</strong> Matteo Landi details his workflow using `.plan` files—simple plaintext files for daily tasks, ideas, and debugging notes, inspired by John Carmack. He employs a Markdown-like format, syncs via Dropbox, and uses Vim with custom highlighting, advocating for consistent note-taking to improve technical writing and organization.</p>
<p><strong>The Lobsters Take:</strong> One user, Xophmeister, commented on trying `.plan` files but eventually moving to Logseq to ensure consistent usage.</p>
<p><a href="https://lobste.rs/s/zgdpht/plan_files_2020">Comments on Lobsters</a></p>]]></description>
      <pubDate>Thu, 12 Feb 2026 16:18:47 -0600</pubDate>
      <guid>https://lobste.rs/s/zgdpht</guid>
      <comments>https://lobste.rs/s/zgdpht/plan_files_2020</comments>
    </item>
    <item>
      <title>The Timeless Way of Programming (2022)</title>
      <link>https://tomasp.net/blog/2022/timeless-way/</link>
      <description><![CDATA[<p><strong>The Gist:</strong> Tomas Petricek explores Christopher Alexander's "The Timeless Way of Building" in the context of software development. He contrasts "explicit modernism" (reinventing forms) with "implicit modernism" (using living pattern languages). Petricek suggests software could benefit from a "slow software" approach—egoless, evolving, and community-maintained, similar to traditional architecture. He also discusses the concept of shared pattern languages, like F# idioms, and adaptable modular components.</p>
<p><strong>The Lobsters Take:</strong> No comments yet.</p>
<p><a href="https://lobste.rs/s/1nqt8w/timeless_way_programming_2022">Comments on Lobsters</a></p>]]></description>
      <pubDate>Thu, 12 Feb 2026 15:16:56 -0600</pubDate>
      <guid>https://lobste.rs/s/1nqt8w</guid>
      <comments>https://lobste.rs/s/1nqt8w/timeless_way_programming_2022</comments>
    </item>
  </channel>
</rss>

state.json

{
  "lastProcessedGuids": [
    "https://lobste.rs/s/vxkq0z",
    "https://lobste.rs/s/fna9yv",
    "https://lobste.rs/s/i0xmbk",
    "https://lobste.rs/s/0fjf0h",
    "https://lobste.rs/s/jagwef"
  ],
  "lastRun": "2026-02-12T09:07:00-08:00"
}