The Nixpkgs core team has disbanded
The Nixpkgs core team announced its disbandment, citing unsustainable workload and attrition after ten months of operation. Their achievements included reforming the committer‑delegation process, onboarding 19 new committers, extending the merge bot, re‑establishing GitHub contact, securing an Enterprise Cloud upgrade, handling the GHSA‑67f2‑674w‑6g63 security incident, and drafting an initial automation/AI policy. The team attributes its dissolution to systemic governance problems with the NixOS Steering Committee (SC): inadequate delegation, micromanagement, unclear communication, delayed responses, and poor coordination on GSoC, grant initiatives, AI policy, moderation, and GitHub organization reforms. These issues impeded the team’s constitutional mandate of project direction, decision‑making, and coordination with the NixOS Foundation Board. The core team argues that its high‑trust consensus model yielded effective resolutions, but persistent SC shortcomings caused burnout and reduced contributor engagement. Members will reduce Nixpkgs involvement, will not seek SC seats, and leave the SC as the final backstop, hoping future governance will enable delegated, technically focused leadership.
NASA to keep its 48-year-old Voyager 2 probe running for yet another year
NASA’s “Big Bang” power‑conservation update reduces Voyager 2’s electricity demand by disabling non‑science hardware and switching to lower‑power alternatives that still maintain spacecraft thermal balance. The radioisotope thermoelectric generators on both Voyagers lose about 4 W per year, forcing the team to cut power margins to a “razor‑thin” level. Since 2024 each probe has already been forced to shut down two scientific instruments; Voyager 2 now operates only three instruments, but the new power shifts should keep all three functional for at least another year. Voyager 2, now ~142 AU from the Sun, will receive the same treatment as Voyager 1, which is ~171 AU away and will be re‑programmed in the coming months. Both probes, launched in 1977, used RTGs for power, completed planetary flybys (Voyager 2’s last in 1989), and entered interstellar space (Voyager 2 in 2018, Voyager 1 in 2012). One‑way communications take roughly 24 hours.
The comments discuss informal staffing of small JPL research projects, noting reliance on part‑time engineers outside official channels and limited dedicated resources. A specific developer who previously encoded Voyager 2 command sequences is highlighted, with concerns about her continued involvement. The conversation also references Voyager 2’s upcoming instrument shutdown and power adjustments, mentions a documentary recommendation, and includes a lighthearted suggestion for a commemorative coffee mug. Overall, the tone reflects awareness of resource constraints and appreciation for legacy expertise.
DeepSeek V4 Flash 0731
DeepSeek V4 Flash 0731 – ARC‑AGI Results is presented as a brief announcement accompanied by a call‑to‑action for the ARC Prize newsletter. The page invites users to subscribe for official contest updates, emphasizing that communications are spam‑free and can be unsubscribed at any time. Visual elements include two images identified only by their alternative text: “ARC Prize Verified” and “ARC Prize.” No further technical details, performance metrics, or analysis of the DeepSeek V4 Flash model are provided in the scraped excerpt. The content is limited to the title, subscription prompt, and minimal image descriptors.
Overall sentiment is largely positive, highlighting DeepSeek V4 Flash 0731’s low cost, high speed, and strong programming assistance, which many users say enables extensive automation, CI integration, and local deployment without expensive hardware. Common praise focuses on its token efficiency, fast prefill rates, and usefulness for coding and data analysis. Recurrent concerns include occasional tool‑calling slowness, infinite loops, blind‑spot errors, and uncertainty about upcoming price hikes. Opinions on benchmark rankings are split, with some viewing it as near‑state‑of‑the‑art and others questioning its real‑world reliability. The model is regarded as a valuable, cost‑effective option despite noted limitations.
U.S. Department of Energy Launches the Genesis Open Models Initiative
Comments focus on the scarcity of American open‑weight models, noting recent efforts such as Inkling and questioning their performance goals, scaling strategy, and niche. Several remarks highlight restrictions on Chinese models at U.S. labs and suggest that alternatives could fill gaps, while also asking whether Europe offers similar programs and how architectural or data differences affect results. There is a call for stronger incentives, like funding postdocs, to encourage contributions. A separate criticism describes unproductive interactions with Department of Energy personnel, contrasting them with private‑sector AI behavior. Overall, the discussion blends analytical curiosity with concerns about policy, collaboration, and support structures.
Physicist Rigged His Pet Hamster's Wheel to Strava. It Runs Far Every Night
Thijs de Buck, an MRI physicist in Utrecht, rigged his hamster Mollie’s wheel with a magnet and hall‑sensor that feed rotation data to an ESP32 microcontroller. A nightly script converts the counts into a Strava‑compatible .FIT file and uploads it via the Strava API. Initial attempts with a cheap bicycle computer failed because its sensor entered standby after five minutes of inactivity and only reported total distance. The custom system provides live speed on an OLED display, automated personal‑best tracking, and selectable run titles. Recorded activities show Mollie running 5.5–6 miles (≈9–10 km) over 3.5–4.5 hours per night, with a peak of 10.8 km in the first week. The hamster’s Strava account, which required a paid subscription, quickly amassed thousands of likes, 1,200 kudos and 600 followers, and completed Strava’s 400‑minute challenge in two days. De Buck, an avid runner, plans to compare his weekly mileage to Mollie’s and to test the platform’s race‑time predictions.
The discussion centers on a DIY pet‑exercise‑wheel tracker built with an ESP32, hall sensor and magnet, logging rotation timestamps and exporting them to Strava as .FIT files. The author highlights prior coverage on Hackaday, adds a treat dispenser for motivation, and shares code and setup details via Reddit. The tone is enthusiastic and informative, emphasizing the novelty of applying fitness‑tracking tools to a cat and hamster without presenting criticism or alternative viewpoints.
SupererDuperer
SuperDuper 4 is a complete ground‑up rewrite of the SuperDuper backup utility, now requiring macOS 14 (Sonoma) or later. It replaces the legacy document model with “Copy Jobs” organized by source, offering inline configuration via clickable links that instantly update the “What’s going to happen?” preview. A dedicated Preview mode runs a dry‑run and reports pending changes. Performance has been dramatically improved: Smart Updates are 2‑10× faster, and the new Turbo feature can reduce a typical 2.5 TB, 8‑million‑file nightly update from 40 minutes to about one minute. The architecture separates the copy engine (a background helper/server) from the UI, allowing backups to continue after the app quits or the user logs out, and supports simultaneous multiple jobs. File‑system support now includes any macOS‑compatible volume (e.g., exFAT, network shares). Copy Rules replace scripts, enabling granular inclusion/exclusion with live previews, and Shortcuts integration allows pre‑ and post‑copy actions, including email notifications or custom scripts. SuperDuper 4 is a paid upgrade (free for recent purchasers or qualifying users), while unregistered users retain full bootable backup capability.
The comments express strong approval of SuperDuper’s recent updates, highlighting Dave’s preservation of core features such as the “what’s going to happen next” preview and enhancements to its backup capabilities. Users appreciate the tool’s ability to handle numerous edge cases across varied drives, filesystems, and macOS versions, noting that it reduces typical troubleshooting and simplifies occasional backups. The overall sentiment is that SuperDuper represents a reliable, well‑engineered solution, making it a highly recommended purchase.
Assembly Hall of Shame
The “Assembly Hall of Shame” (github.com/xoreaxeaxeax/asm‑hall‑of‑shame) benchmarks the absolute worst‑case latency of single x86 instructions by crafting micro‑architectural stalls rather than optimizing speed. Each entry records a single scored instruction, the timing method, and the resulting cycle count (normalized to the CPU base clock).
Key strategies include: loading 512 B FPU/MMX/XMM state with fxrstor64 from a high‑latency PCIe MMIO region while other cores hammer a different MMIO register, forcing the load to queue behind non‑posted transactions; unaligned vmovdqu loads that trigger GPU‑side non‑posted accesses; lock‑prefixed memory ops straddling cache‑line boundaries to invoke external bus locks; subnormal floating‑point operands that invoke microcode assists; saturating write‑combining buffers with many movnti stores followed by mfence; exhaustive cache dirtying to force DRAM write‑back; MSR writes to high‑latency registers (e.g., MCG_CTL); and exhausting the hardware entropy pool.
Reported latencies range from 1 cycle (nop) to 198 000 000 000 000 cycles (≈62 s) on an AMD Ryzen 7 5800H using the fxrstor64 + MMIO hammer technique. The project is authored by Christopher Domas.
The comments focus on the phenomenon of unusually slow processor instructions and their use in performance‑deoptimization contests. Contributors note that bus cycles can be arbitrarily long, reference specific examples such as fxrstor64 and nop, and discuss measurement techniques like rdtsc. Several participants question the relevance of MMIO‑based tests, suggesting memory‑only variants would be more interesting, while others express curiosity about cross‑architecture differences. The thread also includes brief acknowledgments of the author’s other projects and mixed reactions ranging from admiration to criticism of perceived spam.
Ancient Library – 1,060 Greek/Latin texts, click any word to parse it
The Ancient Library provides a comprehensive parsing reader for classical Greek and Latin literature. Users can click any word within the texts to access its lemma, morphological analysis, and full dictionary entry—using Lewis & Short for Latin and Liddell‑Scott‑Jones for Greek. The collection comprises 1,060 works, including 293 Latin texts and 767 Greek texts authored by roughly 140 writers. An A–Z index enables browsing the entire corpus, and separate sections allow navigation of Latin and Greek materials. The platform serves scholars and students seeking original-language access with integrated lexical tools.
The comments show strong enthusiasm for the ancient‑text tool, with many users appreciating its ability to simplify reading Greek and Latin and expressing interest in extending it with features such as improved fonts, macrons, vowel lengths, better dictionary pop‑ups, in‑context highlights, chapter markers, sorting by date, and integration of maps, Anki decks, and critical apparatus. Repeated criticisms focus on the current Greek font, accent rendering, spacing, and limited formatting, while suggestions include adding interlinear glosses, bilingual displays, and smoother navigation. Overall the consensus is that the concept is valuable but requires substantial polishing and feature expansion.
What happens if an entire class of workers loses faith in their careers
The essay describes a growing existential discontent among knowledge workers who, despite high salaries, find their jobs increasingly meaningless—a condition the author labels “Workism,” where work substitutes for spiritual fulfillment. Citing Derek Thompson’s “American Workism” and David Graeber’s “Bullshit Jobs,” it argues that many modern roles (finance, consulting, tech) lack altruistic purpose, fostering melancholy and a desire for analog hobbies. The advent of AI agents now automates not only routine tasks but also higher‑level outputs (strategies, marketing campaigns), pushing workers farther from direct creation and intensifying the illusion of productivity. The piece distinguishes “outcome‑first” workers, who prioritize efficiency, from “experience‑first” workers, who value the collaborative, messy middle that fuels creativity, referencing Teresa Amabile’s intrinsic motivation research. It warns that AI‑driven efficiency could erode this environment, risking talent loss and a broader collapse of Workism. To counter, the author suggests preserving human interaction, embracing slower, exploratory work, and recognizing work as a spectacle rather than a source of ultimate meaning.
The comments convey a broadly uneasy mood about the perceived erosion of purpose in knowledge work, especially as AI and automation displace roles and amplify a toxic online environment. Many draw parallels to historical trade‑skill losses, cite remote‑work isolation, and describe burnout, loss of community, and declining compensation as contributing to existential doubt. While some view AI as a useful tool or an opportunity for new creative projects, a sizable portion express skepticism that meaningful, fulfilling employment remains viable without drastic personal or societal change.
Managing AI Coding Costs at Scale
Managing AI coding tools at scale creates a cost paradox: productivity gains are offset by rapidly rising expenses. Companies address this by targeting the “efficiency frontier,” selecting models that deliver required coding quality at the lowest price per inference. Key techniques include: (1) adopting newer open‑source or lower‑cost models after internal benchmarking; (2) using flexible tooling such as meta‑harnesses (e.g., Databricks Omnigent) that allow seamless model switching; (3) implementing dynamic request or task routing—request‑level proxies, meta‑harness task routing, and escalation patterns—to dispatch work to the cheapest capable model, with reported >30 % average cost reductions; (4) providing developers with real‑time spend visibility, progressive spend gates, and down‑shifting to cheaper models rather than hard caps; (5) reducing token overhead via context compression, less‑chatty harnesses, tool output auditing, and tuned prompt caching, achieving up to ~50 % token‑cost cuts. These controls are unified in an AI Gateway architecture (e.g., Databricks Unity AI Gateway) that manages model catalogs, budget enforcement, configuration, and logging. The combined playbook enables broad, low‑friction AI access while keeping aggregate costs within predictable bounds.
Comments reflect mixed views on extensive AI‑driven development. Many acknowledge notable productivity gains and the ability to produce work comparable to several senior engineers, yet emphasize rising token costs and the need for vigilant budgeting. Concerns arise about long‑term maintainability of heavily agent‑generated code, especially in large, complex codebases, and skepticism is expressed regarding the sustainability and valuation of major AI providers. Participants also discuss the importance of internal benchmarks, token‑efficiency strategies, and the trade‑offs between using high‑performance models versus cheaper alternatives.
The comments express mixed sentiment about the recent dissolution of the Nixpkgs core team. Contributors acknowledge the valuable work done and note burnout as a key factor, while many voice concern over governance shortcomings, perceived micromanagement, and community toxicity that have eroded trust. Some highlight continued strong corporate adoption and the technical strengths of Nix, yet others question future maintenance, update frequency, and overall stability. Overall, there is a desire for clearer, more sustainable governance and healthier community dynamics to preserve the ecosystem.