Skip to content

Instantly share code, notes, and snippets.

@puf
Last active March 11, 2026 05:17
Show Gist options
  • Select an option

  • Save puf/0acff45b98d3eacd2bf56566884c90cc to your computer and use it in GitHub Desktop.

Select an option

Save puf/0acff45b98d3eacd2bf56566884c90cc to your computer and use it in GitHub Desktop.
Lobsters Digest (AI)
<?xml version='1.0' encoding='UTF-8'?>
<rss version="2.0">
<channel>
<item><title>Tony Hoare (1934-2026)</title><link>https://blog.computationalcomplexity.org/2026/03/tony-hoare-1934-2026.html</link><description>&lt;p&gt;&lt;strong&gt;The Gist:&lt;/strong&gt; Turing Award winner and former Oxford professor Tony Hoare passed away last Thursday at the age of 92. Hoare is renowned for his work on quicksort and other significant contributions to computer science.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The Lobsters Take:&lt;/strong&gt; The discussion includes personal tributes and reflections on Tony Hoare's legacy, such as one user's admiration for his enduring intellect and a &lt;a href="https://lobste.rs/c/vzzygw"&gt;freshman college experience&lt;/a&gt; where Hoare demonstrated great politeness and generosity. Initially, there was some skepticism regarding the announcement's veracity due to a lack of immediate official sources, as noted in &lt;a href="https://lobste.rs/c/yunufu"&gt;one comment&lt;/a&gt;. However, this was clarified by a user who pointed out that Jim Miles, a personal acquaintance, had firsthand confirmation of Hoare's passing (&lt;a href="https://lobste.rs/c/lce2gj"&gt;comment here&lt;/a&gt;). Another user provided &lt;a href="https://lobste.rs/c/86cmbz"&gt;links&lt;/a&gt; to valuable resources, including the preface of "Theories of Programming: The Life and Works of Tony Hoare" and his Turing Award page, for those wishing to learn more about his career.&lt;/p&gt;</description><pubDate>Tue, 10 Mar 2026 10:42:09 -0500</pubDate><guid>https://lobste.rs/s/lyktdk</guid><comments>https://lobste.rs/s/lyktdk/tony_hoare_1934_2026</comments></item><item><title>RISC-V is sloooow</title><link>https://marcin.juszkiewicz.com.pl/2026/03/10/risc-v-is-sloooow/</link><description>&lt;p&gt;&lt;strong&gt;The Gist:&lt;/strong&gt; Marcin Juszkiewicz, an AArch64 porter for Fedora Linux, discusses his experience with RISC-V development, particularly focusing on its current performance limitations. He highlights the significant difference in package build times between RISC-V and other architectures (e.g., aarch64, x86_64), with RISC-V taking considerably longer (143 minutes for binutils vs. 36 minutes for aarch64). This slowness necessitates disabling Link Time Optimization (LTO) to manage memory usage and build times. While acknowledging upcoming hardware improvements like UltraRISC UR-DP1000 and SpacemiT K3, he stresses the need for more powerful, rackable, and manageable RISC-V server hardware to make it a primary architecture for Fedora Linux. He also notes that QEMU emulation with many cores can sometimes outperform actual RISC-V hardware for building heavy packages like LLVM.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The Lobsters Take:&lt;/strong&gt; The discussion revolves primarily around the current state of RISC-V performance and its practical implications, with some skepticism regarding its immediate viability as a workstation alternative. Commenters express frustration with the "just around the corner" narrative, pointing out that currently available RISC-V hardware significantly lags behind x86_64 and AArch64 offerings in performance (see &lt;a href="https://lobste.rs/c/suqbvf"&gt;this comment&lt;/a&gt; for a detailed comparison of current RISC-V SBCs to Raspberry Pi generations). There's debate on whether RISC-V's current slowness hinders its adoption in projects like Fedora Linux, with some arguing that slow iteration speed can kill a project and that maintainers should focus on more widely used architectures (&lt;a href="https://lobste.rs/c/6chckw"&gt;comment&lt;/a&gt;). Others question the premise, suggesting that Fedora's stance implies an inability to administer systems that aren't "fast enough" (&lt;a href="https://lobste.rs/c/ix3p22"&gt;comment&lt;/a&gt;). Some commenters highlight the cost-effectiveness of RISC-V hardware, suggesting that a build farm of multiple cheaper RISC-V boards could be a viable alternative to expensive high-core x86 machines (&lt;a href="https://lobste.rs/c/6zww6y"&gt;comment&lt;/a&gt;). The consensus appears to be that while RISC-V has great potential and is a "humongous step forward" for non-performance-bound computing, a parity RISC-V core comparable to high-end x86 or AArch64 systems does not yet exist (&lt;a href="https://lobste.rs/c/iykjnx"&gt;comment&lt;/a&gt;).&lt;/p&gt;</description><pubDate>Tue, 10 Mar 2026 14:49:53 -0500</pubDate><guid>https://lobste.rs/s/ta3jjk</guid><comments>https://lobste.rs/s/ta3jjk/risc_v_is_sloooow</comments></item><item><title>AI should help us produce better code</title><link>https://simonwillison.net/guides/agentic-engineering-patterns/better-code/</link><description>&lt;p&gt;&lt;strong&gt;The Gist:&lt;/strong&gt; Simon Willison argues that AI, specifically coding agents, should help developers produce *better* code, not worse. He counters the fear that AI will lead to a drop in quality by stating that shipping worse code with agents is a choice, and we can choose to ship better code instead. Willison emphasizes that coding agents are ideal for tackling "simple but time-consuming" technical debt fixes, such as refactoring, renaming concepts, combining duplicate functionality, or splitting large files. He suggests that the cost of these improvements has dropped significantly, allowing for a "zero tolerance attitude to minor code smells." Furthermore, AI tools can help consider more options during planning and facilitate exploratory prototyping, allowing developers to quickly test multiple solutions. He advocates for "Compound Engineering," where lessons learned from agent runs are documented to improve future results, leading to a continuous increase in codebase quality.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The Lobsters Take:&lt;/strong&gt; The discussion largely revolves around the implications of AI on code quality, developer learning, and technical debt. Many commenters echo the article's sentiment that AI can improve code quality and reduce technical debt. One user states, "&lt;a href="https://lobste.rs/c/pv8zin"&gt;AI makes me care more about code quality&lt;/a&gt;," while another notes that they can now address cross-codebase changes and refactoring at a scale previously "psychologically balked at" because of agents. One user highlights that LLMs help them write code faster by avoiding "silly" bugs, automating plumbing, and ensuring good error messages and documentation. The sentiment of AI assisting learning is also present, with a commenter optimistically comparing it to how "&lt;a href="https://lobste.rs/c/iroex0"&gt;calculators didn't stop motivated people from learning mathematics&lt;/a&gt;."&lt;/p&gt;
&lt;p&gt;However, some concerns are raised, particularly regarding new developers and the understanding of code quality. A user questions, "&lt;a href="https://lobste.rs/c/f2g9wg"&gt;how is that person expected to learn the code?&lt;/a&gt;" and "&lt;a href="https://lobste.rs/c/8oogvt"&gt;how will someone know that the code is bad without learning how to program first?&lt;/a&gt;" Another commenter touches on the subjective nature of "good" code, pointing out that "&lt;a href="https://lobste.rs/c/xbsqjf"&gt;"Bad" and "good" code aren't well defined. These are aesthetic qualities.&lt;/a&gt;" The article's assertion about avoiding technical debt entirely is also debated, with a user stating that it's "&lt;a href="https://lobste.rs/c/9l3muq"&gt;as idealistic as it was pre agents&lt;/a&gt;," but agrees that agents make paying down debt much quicker. The discussion also touches on agent-based PR review and the potential for agents to regularly review code for architectural or performance issues.&lt;/p&gt;</description><pubDate>Tue, 10 Mar 2026 17:38:37 -0500</pubDate><guid>https://lobste.rs/s/tiktds</guid><comments>https://lobste.rs/s/tiktds/ai_should_help_us_produce_better_code</comments></item><item>
<title>RISC-V is sloooow</title>
<link>https://lobste.rs/s/ta3jjk/risc_v_is_sloooow</link>
<guid>ta3jjk</guid>
<pubDate>Tue, 10 Mar 2026 14:49:53 -0500</pubDate>
<description>**The Gist:** The author, an ARM developer, shares their experience working with the RISC-V port of Fedora Linux over three months. While they've successfully triaged bugs and sent 86 pull requests for Fedora packages, a significant challenge is the "sloooow" performance of current RISC-V hardware, leading to drastically longer build times compared to aarch64, i686, ppc64le, s390x, and x86_64 architectures. For instance, building the binutils package takes 143 minutes on RISC-V, versus 25-46 minutes on others. This slowness necessitates disabling Link Time Optimization (LTO) to conserve memory and reduce build times. Current RISC-V builders typically have 4 or 8 cores and 8-32GB RAM, with performance comparable to older Arm Cortex-A55 cores. Newer SoCs like UltraRISC UR-DP1000 and SpacemiT K3 are expected to improve the situation but aren't seen as a "final solution." The author emphasizes the need for rackable, manageable hardware capable of building packages like binutils in under an hour with LTO enabled for RISC-V to become a primary Fedora architecture. QEMU with 80 emulated cores is still faster for some builds (e.g., llvm15 takes 4 hours on QEMU vs. 10.5 hours on a Banana Pi BPI-F3). Future plans include building Fedora 44, initially with LTO still disabled, and bringing in faster builders.
**The Lobsters Take:** The comments revolve around the central theme of RISC-V's current performance limitations.
* **classichasclass** [link to comment kvfuvl] directly challenges RISC-V enthusiasts to name a workstation-comparable RISC-V chip available today, expressing fatigue with promises of future improvements and noting that current offerings seem to compete with Raspberry Pi. They mention still using a POWER9, indicating a willingness to invest in alternatives if viable.
* **alexrp** [link to comment yfnlhj] agrees that claims of immediate x86/AArch64 comparable performance are "borderline insane." They point to the upcoming Tenstorrent Atlantis silicon dev platform as a promising development for acceptable daily use performance and a potential replacement for slow Milk-V Jupiters in CI.
* **brucehoult** [link to comment suqbvf] explains that RISC-V is extremely new, citing that the first $100 RISC-V SBC was equivalent to a 2012 Raspberry Pi (9 years behind), and a more recent Milk-V Megrez (shipping January 2025) is equivalent to a mid-2019 Raspberry Pi 4 (5.5 years behind), indicating the significant catching up required.</description>
</item>
<item>
<title>LLM Neuroanatomy: How I Topped the AI Leaderboard Without Changing a Single Weight</title>
<link>https://lobste.rs/s/zzjjyo/llm_neuroanatomy_how_i_topped_ai</link>
<guid>zzjjyo</guid>
<pubDate>Tue, 10 Mar 2026 15:12:41 -0500</pubDate>
<description>**The Gist:** The article "LLM Neuroanatomy: How I Topped the AI Leaderboard Without Changing a Single Weight" by David Noel Ng describes how the author achieved the top spot on the HuggingFace Open LLM Leaderboard with the model `dnhkng/RYS-XLarge` without altering any model weights or performing new training. The innovation involved duplicating a specific seven-layer block from an existing 72-billion parameter model and re-integrating it. This technique, termed "LLM Neuroanatomy," was inspired by observations such as an LLM's unexpected ability to process and respond to Base64 encoded input, suggesting a deeper internal understanding despite the format being out-of-distribution for its training.
**The Lobsters Take:**
* **thesnarky1** found the article "fascinating" for its deep dive into model structure and the impact of structural changes, distinguishing it from typical "vibecoding" articles.
* **kornel** expressed concern over Transformer architecture allocating equal compute to simple and complex tasks, and suggested that dynamically selecting the number of loops or skipping layers (MoE style) could be a logical next step given the fascinating discovery of layer looping.
* **skycam** pondered whether a similar method could identify and replace redundant layers with pointers, potentially reducing memory requirements without the performance sacrifices often associated with traditional pruning.</description>
</item>
<item>
<title>Source-available projects and their AI contribution policies</title>
<link>https://lobste.rs/s/ysvfji/source_available_projects_their_ai</link>
<guid>ysvfji</guid>
<pubDate>Tue, 10 Mar 2026 10:45:04 -0500</pubDate>
<description>**The Gist:** A survey of 112 major source-available projects revealed that 71 had explicitly AI-assisted commits, with many more allowing AI contributions without clear labeling. Only 4 projects (Zig, NetBSD, GIMP, qemu) entirely banned AI contributions, while some like DuckDB and Elasticsearch had AI commits despite policies seemingly against them. The survey found no clear pattern in AI adoption or banning across low-level and high-level projects. It notes that "Not found" in the data indicates no explicit policy or accepted AI contributions were identified. The article provides a table detailing AI contribution policies and accepted AI-assisted commits for various programming languages, web browsers, and databases, including preferred AI providers where mentioned.
**The Lobsters Take:** The author, eatonphil, clarified that their survey found 70 of 112 projects already had AI-assisted commits, while 4 banned them. They noted that surveying distributions like Gentoo for AI policies was harder due to distributed codebases. The author emphasized that the survey makes no judgment. Another user, eminence32, questioned the classification of "llama.cpp" in the survey, pointing out a discrepancy between its policy ("does not accept pull requests that are fully or predominantly AI-generated. AI tools may be utilized solely in an assistive capacity.") and the survey's "Allows AI contributions = yes (AI-assisted)" label. They also couldn't find explicit preferred AI providers (Claude, Gemini) mentioned for llama.cpp.</description>
</item>
<item>
<title>Dependency Tracking is Hard</title>
<link>https://lobste.rs/s/lsjk8m/dependency_tracking_is_hard</link>
<guid>lsjk8m</guid>
<pubDate>Tue, 10 Mar 2026 03:47:35 -0500</pubDate>
<description>**The Gist:** The provided article content snippet primarily contains CSS and HTML boilerplate, with the title "Dependency Tracking is Hard" from `daniel.haxx.se`. The actual body of the article content is not available in the snippet, preventing a detailed summary of the article itself.
**The Lobsters Take:** The discussion revolves around the article's premise that "dependency tracking is hard." Commenters question whether the article adequately considers traditional package managers like `dpkg`, `RPM`, `ports`, and `Nix`, which are designed for robust dependency management. `iv` suggests the article might be focusing on the challenge of tracking *vendored* dependencies (those bundled directly with a project or OS rather than installed via a package manager). `technomancy` points out that distributions like Debian package `curl` normally, making its dependencies clear, and finds it odd if the article's tools or screenshots ignore `apt` given its widespread use. `untitaker` adds that expecting upstream software to "support" specific package managers like `apt` is unusual, as many projects don't maintain distro-specific packages.</description>
</item>
<item>
<title>Rebasing in Magit</title>
<link>https://lobste.rs/s/5mf3cb/rebasing_magit</link>
<guid>5mf3cb</guid>
<pubDate>Tue, 10 Mar 2026 09:05:15 -0500</pubDate>
<description>**The Gist:** The article "Rebasing in Magit" by kqr, published on 2026-03-10, highlights the discoverability and efficiency of using Magit for Git operations, specifically focusing on the `git log` command within Magit. The author, inspired by Ian Whitlock's article on Magit, explains how Magit provides unintrusive hints for various `git log` options, making complex commands easily discoverable without needing to memorize man pages. Examples include filtering by author, date range, and file paths. The article emphasizes that Magit transparently shows the underlying Git commands it executes, helping users understand Git CLI better rather than hindering it. It sets the stage for discussing rebasing by first establishing the importance and power of Magit's `git log` interface for understanding repository structure.
**The Lobsters Take:** The comments section shows strong appreciation for Magit. User "untrusem" mentions Magit (and ediff) being crucial for a 2-year-old fork rebase and praises its ability to teach Git, citing `--autostash` as an example. "slondr" extends this, noting that `M-x magit-clone` offers a superior directory picker than the terminal. "ubernostrum" points out a VS Code extension that mimics the Magit experience for those who don't use Emacs. "aardvark179" acknowledges Magit's excellence for rebasing but notes that some complex scenarios, like type renames, still occasionally require exporting patches and manual search/replace.</description>
</item>
<item>
<title>RISC-V is sloooow</title>
<link>https://lobste.rs/s/ta3jjk/risc_v_is_sloooow</link>
<guid>ta3jjk</guid>
<pubDate>Tue, 10 Mar 2026 14:49:53 -0500</pubDate>
<description>Summary unavailable.</description>
</item>
<item>
<title>LLM Neuroanatomy: How I Topped the AI Leaderboard Without Changing a Single Weight</title>
<link>https://lobste.rs/s/zzjjyo/llm_neuroanatomy_how_i_topped_ai</link>
<guid>zzjjyo</guid>
<pubDate>Tue, 10 Mar 2026 15:12:41 -0500</pubDate>
<description>Summary unavailable.</description>
</item>
<item>
<title>Source-available projects and their AI contribution policies</title>
<link>https://lobste.rs/s/ysvfji/source_available_projects_their_ai</link>
<guid>ysvfji</guid>
<pubDate>Tue, 10 Mar 2026 10:45:04 -0500</pubDate>
<description>Summary unavailable.</description>
</item>
<item>
<title>Dependency Tracking is Hard</title>
<link>https://lobste.rs/s/lsjk8m/dependency_tracking_is_hard</link>
<guid>lsjk8m</guid>
<pubDate>Tue, 10 Mar 2026 03:47:35 -0500</pubDate>
<description>Summary unavailable.</description>
</item>
<item>
<title>Rebasing in Magit</title>
<link>https://lobste.rs/s/5mf3cb/rebasing_magit</link>
<guid>5mf3cb</guid>
<pubDate>Tue, 10 Mar 2026 09:05:15 -0500</pubDate>
<description>Summary unavailable.</description>
</item>
<title>Lobsters Digest</title>
<link>https://lobste.rs/</link>
<description>Summarized Lobsters feed</description>
<item>
<title>Tony Hoare (1934-2026)</title>
<link>https://blog.computationalcomplexity.org/2026/03/tony-hoare-1934-2026.html</link>
<guid>lyktdk</guid>
<description>
&lt;p&gt;&lt;strong&gt;The Gist:&lt;/strong&gt; A blog post reporting the passing of computer scientist Tony Hoare.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The Lobsters Take:&lt;/strong&gt; The community is discussing the validity of the rumor, noting a lack of official sources like the BBC, and mentioning edit wars on Wikipedia regarding his status. (&lt;a href="https://lobste.rs/s/lyktdk/tony_hoare_1934_2026"&gt;Link to discussion&lt;/a&gt;)&lt;/p&gt;
</description>
</item>
<item>
<title>Amazon holds engineering meeting about GenAI based outages</title>
<link>https://arstechnica.com/ai/2026/03/after-outages-amazon-to-make-senior-engineers-sign-off-on-ai-assisted-changes/</link>
<guid>t5dvs5</guid>
<description>
&lt;p&gt;&lt;strong&gt;The Gist:&lt;/strong&gt; Amazon is reportedly making senior engineers sign off on AI-assisted changes after GenAI-based outages.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The Lobsters Take:&lt;/strong&gt; Discussions likely revolve around the reliability of AI-generated code and the necessity of human oversight in large-scale engineering systems.&lt;/p&gt;
</description>
</item>
<lastBuildDate>Wed, 11 Mar 2026 05:15:21 GMT</lastBuildDate></channel>
</rss>
{
"lastChecked": 1773206121,
"items": {
"https://lobste.rs/s/wepiig": {
"title": "Breaking Down CVE-2026-25049: How TypeScript Types Failed n8n's Security",
"comments": 0
},
"https://lobste.rs/s/vvg4oz": {
"title": "The Transducer That Ate Our Heap",
"comments": 0
},
"https://lobste.rs/s/duogbk": {
"title": "simple email API for protonmail custom domains via proton bridge",
"comments": 0
},
"https://lobste.rs/s/gx9hvu": {
"title": "How to level up the fediverse",
"comments": 1
},
"https://lobste.rs/s/kbf0f4": {
"title": "How I built Fluxer, a Discord-like chat app",
"comments": 0
},
"https://lobste.rs/s/wcak3g": {
"title": "Hylo: A Systems Programming Language All in on Value Semantics and Generic Programming",
"comments": 0
},
"https://lobste.rs/s/kjbrep": {
"title": "The Day the telnet Died",
"comments": 0
},
"https://lobste.rs/s/ogr30w": {
"title": "How I Cut My Google Search Dependence in Half",
"comments": 20
},
"https://lobste.rs/s/elol3n": {
"title": "I Wrote a Scheme in 2025",
"comments": 1
},
"https://lobste.rs/s/pybtso": {
"title": "Go 1.26 is released",
"comments": 1
},
"https://lobste.rs/s/naa5fq": {
"title": "postmarketOS at FOSDEM 2026 + Hackathon",
"comments": 0
},
"https://lobste.rs/s/dlmxra": {
"title": "GitButler CLI Is Really Good",
"comments": 0
},
"https://lobste.rs/s/rqsjod": {
"title": "Proposal: Add Hotness -.25 to Vibe Coding",
"comments": 0
},
"https://lobste.rs/s/r2koiq": {
"title": "What Functional Programmers Get Wrong About Systems",
"comments": 0
},
"https://lobste.rs/s/7iford": {
"title": "I Started Programming When I Was 7. I'm 50 Now, and the Thing I Loved Has Changed",
"comments": 0
},
"https://lobste.rs/s/gipvta": {
"title": "cysqlite - a new sqlite driver",
"comments": 0
},
"https://lobste.rs/s/vrczh6": {
"title": "Discord Launches Teen-by-Default Settings Globally",
"comments": 0
},
"https://lobste.rs/s/hhjrpk": {
"title": "Setting Up Zed",
"comments": 0
},
"https://lobste.rs/s/00edzp": {
"title": "The Missing GitHub Status Page",
"comments": 0
},
"https://lobste.rs/s/t5fcfw": {
"title": "SSH agent forwarding and tmux done right (2023)",
"comments": 0
},
"https://lobste.rs/s/qni92w": {
"title": "How a Bus Route Falls Apart (2025)",
"comments": 0
},
"https://lobste.rs/s/oayzoz": {
"title": "Redefining Go Functions",
"comments": 0
},
"https://lobste.rs/s/9kb1xw": {
"title": "Fine, I'll Try AI",
"comments": 0
},
"https://lobste.rs/s/9dfnqa": {
"title": "FreeBSD Home NAS, part 10: monitoring with VictoriaMetrics and Grafana",
"comments": 0
},
"https://lobste.rs/s/manrbz": {
"title": "Offpunk 3.0",
"comments": 0
},
"https://lobste.rs/s/gtjqqn": {
"title": "Electricity use of AI coding agents",
"comments": 0
},
"https://lobste.rs/s/e5vqhs": {
"title": "Simplifying Vulkan one subsystem at a time",
"comments": 0
},
"https://lobste.rs/s/v59ykl": {
"title": "c-- (2008)",
"comments": 0
},
"https://lobste.rs/s/dsptog": {
"title": "Can my SPARC server host a website?",
"comments": 0
},
"https://lobste.rs/s/6os1a6": {
"title": "A fun Python puzzle with circular imports",
"comments": 0
},
"https://lobste.rs/s/2y5l47": {
"title": "Gentoo on Codeberg",
"processed_at": 1771362698.724948
},
"https://lobste.rs/s/ulht8t": {
"title": "The Servo project and its impact on the web platform ecosystem",
"processed_at": 1771362712.6060538
},
"https://lobste.rs/s/vpbnek": {
"title": "Babashka 1.12.215: Revenge of the TUIs",
"processed_at": 1771362724.758453
},
"https://lobste.rs/s/tt6ieg": {
"title": "Vinyl Cache has left github",
"processed_at": 1771362739.471265
},
"https://lobste.rs/s/vudtax": {
"title": "Plasma 6.6 released",
"processed_at": 1771362750.2740312
},
"https://lobste.rs/s/hax4cv": {
"title": "Undo in Vi and its successors",
"processed_at": 1771362763.274466
},
"https://lobste.rs/s/40ndqz": {
"title": "Using go fix to modernize Go code",
"processed_at": 1771362772.984777
},
"https://lobste.rs/s/ov9qvf": {
"title": "Poor Deming never stood a chance",
"processed_at": 1771362791.648483
},
"https://lobste.rs/s/c6cg0b": {
"title": "The Next Version of Curling IO",
"processed_at": 1771362809.47578
},
"https://lobste.rs/s/2tpg37": {
"title": "How a single typo led to RCE in Firefox",
"processed_at": 1771362824.568788
},
"https://lobste.rs/s/eec8ez": {
"title": "Oat, Ultra-lightweight UI library, Semantic, minimal, zero dependencies",
"processed_at": 1771362844.264868
},
"https://lobste.rs/s/oukhsl": {
"title": "Cryptographic Issues in Matrix\u2019s Rust Library Vodozemac",
"processed_at": 1771391391.382522
},
"https://lobste.rs/s/stgsof": {
"title": "Fast sorting, branchless by design",
"processed_at": 1771391401.353019
},
"https://lobste.rs/s/syv21m": {
"title": "--dangerously-skip-reading-code",
"processed_at": 1771391419.57801
},
"https://lobste.rs/s/pj8faw": {
"title": "6502 Emulation - The Jump Indirect Bug",
"processed_at": 1771391430.641676
},
"https://lobste.rs/s/0xodyl": {
"title": "AI Agent Lands PRs in Major OSS Projects, Targets Maintainers via Cold Outreach",
"processed_at": 1771391441.819072
},
"https://lobste.rs/s/4iqnda": {
"title": "An assembler that compiles to a printf loop",
"processed_at": 1771391452.7911942
},
"https://lobste.rs/s/fwoooe": {
"title": "LeBron James Is President \u2013 Exploiting LLMs via \"Alignment\" Context Injection",
"processed_at": 1771391470.849385
},
"https://lobste.rs/s/zvcupc": {
"title": "Are We Becoming Architects or Butlers to LLMs?",
"processed_at": 1771391485.563225
},
"https://lobste.rs/s/yn5zjh": {
"title": "Terminals should generate the 256-color palette",
"processed_at": 1771391499.420635
},
"https://lobste.rs/s/xqld8c": {
"title": "One page of async Rust",
"processed_at": 1771391511.161568
},
"https://lobste.rs/s/cp1ssa": {
"title": "claimcheck: Narrowing the Gap between Proof and Intent",
"processed_at": 1771420127.055987
},
"https://lobste.rs/s/czch6e": {
"title": "BarraCUDA: Open-source CUDA compiler targeting AMD GPUs (and more in the future!)",
"processed_at": 1771420141.897592
},
"https://lobste.rs/s/rfcbij": {
"title": "15+ years later, Microsoft morged my diagram",
"processed_at": 1771420162.580381
},
"https://lobste.rs/s/8xnajy": {
"title": "What's cooking on SourceHut? Q1 2026",
"processed_at": 1771420191.95259
},
"https://lobste.rs/s/2ssdbm": {
"title": "The case for gatekeeping, or: why medieval guilds had it figured out",
"processed_at": 1771420234.228729
},
"https://lobste.rs/s/idfeqo": {
"title": "Asahi Linux Progress Report: Linux 6.19",
"processed_at": 1771420247.300374
},
"https://lobste.rs/s/osljfj": {
"title": "Understanding Whole Program Paths and Path Profiling",
"processed_at": 1771448912.040975
},
"https://lobste.rs/s/9dgwdo": {
"title": "Bruteforcing the Bitwarden master password I forgor",
"processed_at": 1771448922.874824
},
"https://lobste.rs/s/mv7rkh": {
"title": "Dank Linux - Desktop Environment for Wayland and Niri",
"processed_at": 1771448934.9365811
},
"https://lobste.rs/s/at68gm": {
"title": "F9 Kernel",
"processed_at": 1771448949.59231
},
"https://lobste.rs/s/m2ouss": {
"title": "Current - An RSS reader",
"processed_at": 1771448961.2309911
},
"https://lobste.rs/s/sspnba": {
"title": "What Your Bluetooth Devices Reveal About You",
"processed_at": 1771448973.450161
},
"https://lobste.rs/s/gyyxad": {
"title": "AVX2 is slower than SSE2-4.x under Windows ARM emulation",
"processed_at": 1771448987.945054
},
"https://lobste.rs/s/zk2u9e": {
"title": "DNS-PERSIST-01: A New Model for DNS-based Challenge Validation",
"processed_at": 1771449003.014018
},
"https://lobste.rs/s/axp2rt": {
"title": "Self-hosting my websites using bootable containers",
"processed_at": 1771463344.9282439
},
"https://lobste.rs/s/mzfdcf": {
"title": "130k Lines of Formal Topology in Two Weeks: Simple and Cheap Autoformalization for Everyone?",
"processed_at": 1771463356.6921952
},
"https://lobste.rs/s/shh36u": {
"title": "Top 20 worldwide with social-engineering and a cheat that's still undetected",
"processed_at": 1771463365.4989371
},
"https://lobste.rs/s/zpifkh": {
"title": "Notes on clarifying man pages",
"processed_at": 1771463377.2583091
},
"https://lobste.rs/s/qvjp07": {
"title": "Ditching Discord",
"processed_at": 1771463389.785799
},
"https://lobste.rs/s/rrlcfb": {
"title": "Why I don't think AGI is imminent",
"processed_at": 1771463398.613153
},
"https://lobste.rs/s/w1bsle": {
"title": "Lobsters Interview with steveklabnik",
"processed_at": 1771621961.970904
},
"https://lobste.rs/s/5iucri": {
"title": "\"Made in EU\" - it was harder than I thought",
"processed_at": 1771621961.9709089
},
"https://lobste.rs/s/6yjefp": {
"title": "eBPF the Hard Way",
"processed_at": 1771621961.970911
},
"https://lobste.rs/s/ickplq": {
"title": "Your Personal Blog Should Have Comments",
"processed_at": 1771621961.970913
},
"https://lobste.rs/s/wul2hi": {
"title": "Brat, a parallel TAP testing harness for the POSIX shell",
"processed_at": 1771621961.970915
},
"https://lobste.rs/s/wejtbl": {
"title": "Keep Android Open",
"processed_at": 1771636198.5959601
},
"https://lobste.rs/s/q4ykw7": {
"title": "The Missing Semester of Your CS Education",
"processed_at": 1771636216.892441
},
"https://lobste.rs/s/zkby7e": {
"title": "Lil' Fun Langs",
"processed_at": 1771636228.500046
},
"https://lobste.rs/s/xe7vkq": {
"title": "Django ORM Standalone\u207d\u00b9\u207e: Querying an existing database",
"processed_at": 1771636242.6789482
},
"https://lobste.rs/s/vpxzhe": {
"title": "I found a Vulnerability. They found a Lawyer",
"processed_at": 1771636256.662257
},
"https://lobste.rs/s/t760l8": {
"title": "A Beginner\u2019s Guide to Split Keyboards",
"processed_at": 1771636270.604609
},
"https://lobste.rs/s/i4u55k": {
"title": "finding credentials in .msi files with msiexec",
"processed_at": 1771636280.314306
},
"https://lobste.rs/s/rxsphs": {
"title": "IPv6 Adoption in 2026",
"processed_at": 1771636298.884786
},
"https://lobste.rs/s/bi9wsi": {
"title": "Death to Scroll Fade",
"processed_at": 1771636313.312926
},
"https://lobste.rs/s/gscaw3": {
"title": "Turn Dependabot Off",
"processed_at": 1771636325.801439
},
"https://lobste.rs/s/slfm4t": {
"title": "joinirc.at: Link to your IRC server on any client to onboard new users",
"processed_at": 1771665416.411725
},
"https://lobste.rs/s/zzlxaa": {
"title": "Lindenmayer Systems",
"processed_at": 1771665416.411725
},
"https://lobste.rs/s/gkv4xd": {
"title": "Internationalise The Fediverse (2024)",
"processed_at": 1771665416.411725
},
"https://lobste.rs/s/rcewff": {
"title": "ajail: a basic jail for programs you don't completely trust",
"processed_at": 1771665416.411725
},
"https://lobste.rs/s/wk6rjh": {
"title": "The Claude C Compiler: What It Reveals About the Future of Software",
"processed_at": 1771665416.411725
},
"https://lobste.rs/s/mo0hgf": {
"title": "Justifying text-wrap: pretty",
"processed_at": 1772082715.949715
},
"https://lobste.rs/s/kwpvgy": {
"title": "Goodbye innerHTML, Hello setHTML: Stronger XSS Protection in Firefox 148",
"processed_at": 1772082727.994404
},
"https://lobste.rs/s/8utm05": {
"title": "Tests Are The New Moat",
"processed_at": 1772082740.2994292
},
"https://lobste.rs/s/be27h4": {
"title": "Porting Doom to a 20-year-old VoIP phone",
"processed_at": 1772082751.194325
},
"https://lobste.rs/s/qjl5xc": {
"title": "Your system is fine. Your users aren't",
"processed_at": 1772082761.9039328
},
"https://lobste.rs/s/l4nw7u": {
"title": "Windows 11 Notepad to support markdown",
"processed_at": 1772082773.735693
},
"https://lobste.rs/s/yhv8lq": {
"title": "Against Query Based Compilers",
"processed_at": 1772082786.053918
},
"https://lobste.rs/s/vtyttw": {
"title": "What interesting (and smaller) conferences are there in 2026?",
"processed_at": 1772082797.1843379
},
"https://lobste.rs/s/llboto": {
"title": "Fake Job Interviews Are Installing Backdoors on Developer Machines",
"processed_at": 1772082808.079266
},
"https://lobste.rs/s/bwkwba": {
"title": "New accounts on HN 10x more likely to use EM-dashes",
"processed_at": 1772082822.3722858
},
"https://lobste.rs/s/iedoot": {
"title": "AI=true is an Anti-Pattern",
"processed_at": 1772490319.716793
},
"https://lobste.rs/s/ykwb2z": {
"title": "An AI agent coding skeptic tries AI agent coding, in excessive detail",
"processed_at": 1772490339.130063
},
"https://lobste.rs/s/asryy7": {
"title": "15 Years of Indie Dev In 4 Bits of Advice",
"processed_at": 1772490350.630145
},
"https://lobste.rs/s/szaazg": {
"title": "Custom Data Structures in E-Graphs",
"processed_at": 1772490360.771349
},
"https://lobste.rs/s/3fevyk": {
"title": "fast-servers: an interesting pattern",
"processed_at": 1772490373.822957
},
"https://lobste.rs/s/gpcwus": {
"title": "January in Servo: preloads, better forms, details styling, and more",
"processed_at": 1772490384.7852852
},
"https://lobste.rs/s/kch6lb": {
"title": "Block the \u201cUpgrade to Tahoe\u201d alerts",
"processed_at": 1772490402.081855
},
"https://lobste.rs/s/tza0zh": {
"title": "Yes, and",
"processed_at": 1772490416.171969
},
"https://lobste.rs/s/v5nyjz": {
"title": "prek: a better `pre-commit`",
"processed_at": 1772490432.632499
},
"https://lobste.rs/s/fm1eln": {
"title": "Package Managers \u00e0 la Carte: A Formal Model of Dependency Resolution",
"processed_at": 1772490447.04554
},
"https://lobste.rs/s/of77cp": {
"title": "US Supreme Court declines to hear dispute over copyrights for AI-generated material",
"processed_at": 1772636827.707144
},
"https://lobste.rs/s/r8kjli": {
"title": "Claude is an Electron App because we\u2019ve lost native",
"processed_at": 1772636920.00117
},
"https://lobste.rs/s/tznewb": {
"title": "Nobody Gets Promoted for Simplicity",
"processed_at": 1772636933.0270872
},
"https://lobste.rs/s/ya5b5h": {
"title": "Proposal: Add `Guix` tag",
"processed_at": 1772644262.6574469
},
"https://lobste.rs/s/2ng9uk": {
"title": "RTL: WTF: Read the web like Right-to-Left readers do",
"processed_at": 1772644274.1282308
},
"https://lobste.rs/s/hu6tos": {
"title": "The Markless Document Markup Standard",
"processed_at": 1772644286.550821
},
"https://lobste.rs/s/isuqoa": {
"title": "Never snooze a future",
"processed_at": 1772644299.84566
},
"https://lobste.rs/s/2gwqlh": {
"title": "Rust zero-cost abstractions vs. SIMD",
"processed_at": 1772644311.3667378
},
"https://lobste.rs/s/teexox": {
"title": "Claude's Cycles",
"processed_at": 1772644330.96045
},
"https://lobste.rs/s/hz6vhv": {
"title": "California's Digital Age Assurance Act, and FOSS",
"processed_at": 1772644353.8504
},
"https://lobste.rs/s/zpvdwb": {
"title": "telemetry helps. you still get to turn it off",
"processed_at": 1772822730.3677142
},
"https://lobste.rs/s/efkl8m": {
"title": "A GitHub Issue Title Compromised 4,000 Developer Machines",
"processed_at": 1772822746.365524
},
"https://lobste.rs/s/ncsx3a": {
"title": "GPL upgrades via section 14 proxy delegation",
"processed_at": 1772822761.637849
},
"https://lobste.rs/s/tx3f5n": {
"title": "Ambiguity in C",
"processed_at": 1772822775.7396858
},
"https://lobste.rs/s/m0ajbc": {
"title": "OpenWrt 25.12.0 Released",
"processed_at": 1772822789.056402
},
"https://lobste.rs/s/uwdjjy": {
"title": "A new chapter for the Nix language, courtesy of WebAssembly",
"processed_at": 1772822805.628093
},
"https://lobste.rs/s/e5vqyc": {
"title": "10% of Firefox crashes are caused by bitflips",
"processed_at": 1772822818.7818549
},
"https://lobste.rs/s/msjuyz": {
"title": "EUPL: European Union Public License",
"processed_at": 1772822833.822032
},
"https://lobste.rs/s/lx1wc2": {
"title": "Mozilla is working on a big Firefox redesign, here is what it looks like",
"processed_at": 1772822853.5991292
},
"https://lobste.rs/s/ewojng": {
"title": "XKCD dependency in p5.js",
"processed_at": 1773158987.05292
},
"https://lobste.rs/s/i9akff": {
"title": "Announcing Rust 1.94.0",
"processed_at": 1773159002.986377
},
"https://lobste.rs/s/tiktds": {
"title": "AI should help us produce better code",
"processed_at": 1773206095.457827
},
"https://lobste.rs/s/ta3jjk": {
"title": "RISC-V is sloooow",
"processed_at": 1773206106.915922
},
"https://lobste.rs/s/lyktdk": {
"title": "Tony Hoare (1934-2026)",
"processed_at": 1773206121.147952
}
}
}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment