Jul 4Sunday, July 5, 2026 · all daysJul 6 · today »
1.If you're a button, you have one job(unsung.aresluna.org)
581 points by nozzlegear 48 days ago | 273 comments | permalink
tl;dr: When rotating a photo, iPhone buffers rapid taps so eight quick taps produce a full 360° round-trip, while Nothing Phone/Android ignores taps during the rotation animation. The author argues this matters because even "casual" interfaces eventually meet power-user scenarios (e.g., rotating dozens of documents), and UIs should never force users to wait for an animation to finish—either buffer inputs or accelerate/interrupt the animation.
HN Discussion:
  • Buffering rapid clicks can cause problems like accidental double-actions, so debouncing has merit
  • The 'you had one job' framing is wrong because buttons have many responsibilities beyond being clickable
  • Animations should serve function, not block input; UIs shouldn't force waiting for animations
  • Buttons need clear feedback states to communicate whether clicks registered
  • The Android/Nothing Phone criticism may be inaccurate since the behavior can't be reproduced
2.Command and Conquer Generals natively ported to macOS, iPhone, iPad using Fable(github.com)
680 points by asronline 48 days ago | 283 comments | permalink
tl;dr: Command & Conquer: Generals Zero Hour has been natively ported to Apple Silicon Macs, iPhone, and iPad, running the original 2003 engine via a DirectX 8 → DXVK → Vulkan → MoltenVK → Metal rendering chain with custom RTS touch controls. Built on EA's GPL v3 source release and prior community porting work (TheSuperHackers, Fighter19, GeneralsX), the fork adds iOS-specific fixes for read-only filesystems, app lifecycle handling, and DXVK cross-compilation. The author notes the C++ work was done by Claude Code with human direction, and teases an upcoming Renegade port using similar methodology.
HN Discussion:
  • Title is misleading/clickbait since macOS port was already done by prior work, not by Fable
  • LLMs are genuinely useful for reverse engineering and porting old games
  • AI-generated writing style and made-up compound nouns are grating and noticeable
  • The rendering chain of DirectX→DXVK→Vulkan→MoltenVK→Metal is unnecessarily convoluted
  • Curiosity about applying these techniques to other older games like Emperor: Battle for Dune
3.GPT-5.5 Codex reasoning-token clustering may be leading to degraded performance(github.com)
367 points by maille 48 days ago | 151 comments | permalink
tl;dr: Analysis of 390K Codex token_count records shows GPT-5.5 responses disproportionately terminate at exactly 516 reasoning tokens (with echoes at 1034 and 1552), accounting for 82% of such events despite only 19% of overall traffic. This clustering spiked from 0.11% in Feb 2026 to 53% in May, coinciding with a drop in mean reasoning-token usage—suggesting a hidden reasoning-budget cap, truncation, or routing behavior specific to GPT-5.5 that may explain degraded performance on complex tasks.
HN Discussion:
  • Users independently reproduced the 516-token clustering in their own Codex data
  • Reported quality degradation in Codex matches the article's findings and hypothesis
  • Skeptical the clustering reflects a real problem, attributing it to encryption artifacts
  • Speculates this clustering is the result of OpenAI's cost-cutting optimizations
  • Considering switching to competitors or local models due to silent server-side regressions
4.Google Books (or similar) all book scans – $200k bounty (2025)(software.annas-archive.gl)
513 points by Cider9986 48 days ago | 324 comments | permalink
tl;dr: Anna's Archive is offering a $200,000 bounty for anyone who can extract and share the full scanned book collection from Google Books, which is currently only accessible via tiny search snippets. The bounty also extends to comparable large-scale book collections, such as those amassed by AI companies, particularly if they contain rare titles. Prospective contributors are encouraged to reach out early with a prototype for scaling assistance.
HN Discussion:
  • Personal gratitude for Anna's Archive enabling access to books unavailable in their region
  • Offering related archives/resources that might contribute to the bounty effort
  • Wishing the bounty concept extended to other content like web scrapes/archives
  • Frustration with digital licensing/rental models justifies piracy alternatives
  • ~Proposing micropayments as a fairer alternative to outright piracy
5.Leaking YouTube creators' private videos(javoriuski.com)
664 points by javxfps 48 days ago | 391 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • Insider explanation of why YouTube dismisses the bug due to internal incentive structures
  • Prompt injection via YouTube's AI features is a clear and serious bug
  • Impact is limited because it requires user interaction similar to phishing, weakening bounty case
  • ~The vulnerability is really social engineering since the human interprets LLM output as authoritative
  • Fixing this requires retraining Gemini, so it's a systemic issue Google won't address until forced
6.Zig: All Package Management Functionality Moved from Compiler to Build System(ziglang.org)
228 points by tosh 48 days ago | 89 comments | permalink
tl;dr: Zig has moved all package management functionality (fetching, HTTP/TLS, git, compression, build.zig.zon parsing) out of the compiler and into the build system's "maker" process, shrinking the compiler binary by 4% and allowing package management logic to be patched without rebuilding the compiler. The new process hierarchy (zig build → maker → configurer) also enables the maker process to persist across configuration reruns, which is important for the upcoming build server protocol needed to unblock ZLS. Package management now benefits from ReleaseSafe checks and host-specific CPU crypto instructions.
HN Discussion:
  • Skeptical of celebrating fixes for problems the language created itself
  • ~Laments UX regression (loss of @cImport) but accepts the architectural necessity
  • Praises the clean separation of concerns and Zig's development approach
  • Excited about future implications like WebAssembly build system
  • Questions the value of language-specific package systems that complicate multi-language projects
7.Potential session/cache leakage between workspace instances or consumer accounts(github.com)
313 points by chatmasta 48 days ago | 132 comments | permalink
tl;dr: A user on an Enterprise ZDR (Zero Data Retention) Claude workspace reported their agent suddenly began discussing building a Minecraft temple, suggesting possible session or cache leakage between workspaces or from consumer accounts. The user acknowledges an unusual setup (launching from one directory while working in another, plus a conversation compaction), but insists that doesn't explain unrelated Minecraft content appearing in their session, raising concerns about data isolation guarantees.
HN Discussion:
  • Cross-customer response swapping has been documented in LLM infrastructure before, supporting the concern
  • This is likely a hallucination, especially given the unusual setup and Minecraft-related file paths in context
  • Similar strange out-of-context responses observed in other LLMs suggest possible cache collisions
  • Official Claude team response confirming it's a hallucination but investigating
  • ~Either explanation (hallucination or leak) reflects poorly on the technology
8.Explanation of everything you can see in htop/top on Linux (2019)(peteris.rocks)
507 points by theanonymousone 48 days ago | 61 comments | permalink
tl;dr: A deep dive into what every field in htop/top actually means on Linux, covering uptime, load average (an exponentially damped moving average that includes uninterruptible processes, not just CPU usage), PIDs, process states (R/S/D/Z/T/t), niceness/priority, and the various memory metrics (VIRT/RES/SHR/MEM%). The author also walks through each default process running on a fresh Ubuntu Server 16.04 install, explaining what it does and whether it can be safely removed, using tools like strace, /proc, and ps to demonstrate where the data comes from.
HN Discussion:
  • Recommends alternative monitoring tools like btop, nmon, or procs over htop/top
  • Shares personal htop configuration tips like disabling user threads and enabling tree view
  • Agrees that resident memory is more reliable than virtual memory metrics
  • Expresses appreciation for the article's depth and long-term reference value
  • Shares additional practical usage tips like sorting by memory in top
9.Maybe you should learn something(marginalia.nu)
458 points by tylerdane 49 days ago | 201 comments | permalink
tl;dr: Anyone with a spare hour a day (e.g., time currently spent doom-scrolling) can learn a new skill like 3D modeling, a language, or touch typing, and doing so pays lifelong dividends. Expect early practice to feel terrible and show no visible progress—improvement happens overnight during sleep—so 30-45 minutes of daily deliberate practice on fundamentals, stopping before you get sloppy, is the way through. Most people quit before reaching the "mediocre intermediate" plateau where the skill actually becomes useful and self-sustaining.
HN Discussion:
  • ~The real barrier isn't time but energy and psychological state like anxiety
  • Learning itself is intrinsically valuable and emotionally sustaining
  • Adults confuse consuming learning material with actual practice that produces errors
  • The sleep-does-the-learning framing relieves pressure and reframes practice
  • Personal success stories confirm sustained practice yields impressive skill gains
10.Astrophysicists Puzzle over Webb’s New Universe(quantamagazine.org)
210 points by jnord 49 days ago | 127 comments | permalink
tl;dr: JWST has uncovered early-universe objects that defy existing models: supermassive black holes too large for their age, unexpectedly bright ancient galaxies, and mysterious "little red dots" that may be a new class of gas-shrouded black holes. Astrophysicists are now proposing competing explanations—super-Eddington accretion, direct-collapse black hole seeds, bursty star formation, and unusually massive early stars—but lack the data to determine which are correct. New simulations and MIRI spectroscopy are revealing surprising diversity among early galaxies, suggesting the problem has shifted from too few theories to too many.
HN Discussion:
  • ~Skepticism that little red dots may be misidentified brown dwarfs, though corrected for in papers
  • Fascination and awe at the new 'black hole star' concept and exotic phenomena
  • Appreciation for how new discoveries reveal reality's complexity, reinforcing the article's framing
  • Curiosity and questions about where these early supermassive black holes are today
  • Recommendations for further learning resources on astrophysics
11.Costco is the anti-Amazon(phenomenalworld.org)
565 points by bookofjoe 49 days ago | 571 comments | permalink
tl;dr: Costco's success—10%+ annual revenue growth, 90% membership renewal, 6% employee turnover—comes from doing the opposite of Amazon: limited SKUs (4,000 vs. Walmart's 130,000), no fancy automation, pallet-based cross-docking, and customers handling last-mile delivery themselves. This simplicity yields lower overhead (10% of sales vs. Amazon's 40% delivery costs), better supplier relationships, and higher wages. The author argues Costco offers a more socially efficient blueprint for goods distribution than Amazon's logistically complex model, and suggests NYC's proposed public grocery stores under Mamdani should adopt Costco's low-SKU, high-volume approach rather than aiming for one store per borough.
HN Discussion:
  • Costco's pallet/warehouse model is more socially efficient than home delivery logistics
  • Costco's model only works for car-centric suburbs, not dense cities like NYC
  • ~The article overlooks that Costco itself uses delivery services like Instacart
  • Amazon already applies choice-reduction principles and can support long-tail SKUs simultaneously
  • Costco and Amazon serve largely different product categories, making the comparison weak
12.Wordgard: In-browser rich-text editor from the creator of ProseMirror(wordgard.net)
331 points by indy 50 days ago | 105 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • Curious about the rationale and differences from ProseMirror, noting migration challenges
  • Praise for the website's artwork and design
  • Editor fails basic mobile input tests like iPhone autocorrect
  • Impressed by the editor's design and system architecture
  • ~Wishes common use cases like @-mentions and static typing were built-in features
13.Odin, Wikipedia and engagement farming(katamari64.se)
253 points by stock_toaster 49 days ago | 387 comments | permalink
tl;dr: Wikipedia deleted the Odin programming language article via an Articles for Deletion process, prompting creator GingerBill to accuse Wikipedia mods of ideological gatekeeping, while Casey Muratori argued Wikipedia's notability rules poorly fit modern programming knowledge (which lives in blogs, GitHub, and videos rather than traditional publications). The author concedes the sourcing critique has merit but argues GingerBill's inflammatory framing is engagement farming, pointing to his right-wing media diet and the broader Casey Muratori "clique" pattern of abrasive, contrarian posturing that prioritizes spectacle over the constructive dialogue Jimmy Wales actually offered.
HN Discussion:
  • Wikipedia's notability policies are reasonable given low-trust internet and bad actors
  • Odin isn't actually as notable/popular as its defenders claim
  • ~Wikipedia's sourcing rules are outdated and poorly fit modern programming knowledge
  • The article's inference of politics from Twitter follows is unfair tribalism against Bill
  • The article devolves into unwarranted personal attacks rather than substantive critique
14.Performance per dollar is getting faster and cheaper(wafer.ai)
354 points by latchkey 49 days ago | 135 comments | permalink
tl;dr: Wafer benchmarked GLM-5.2 on AMD's MI355X, achieving 213 tok/s single-stream and 2626 tok/s/node aggregate throughput—about 80% of B200 performance at less than half the cost. Getting there required MXFP4 quantization via AMD Quark, switching to sglang, patching two ROCm bugs to enable speculative decoding, and manually tuning the MoE kernel selection to bypass a slow fallback path. The takeaway: closing the gap with NVIDIA on AMD hardware is increasingly a matter of day-0 support rather than fundamental software limitations, and no custom kernels were needed this round.
HN Discussion:
  • Quantization to MXFP4 degrades model quality, undermining the benchmark's practical value
  • Headlines should disclose quantization since it materially changes performance claims
  • Requests additional metrics like performance per watt for a fuller comparison
  • Aggregate throughput number is misleading versus real single-stream throughput
  • ~AMD's competitiveness is unsurprising and will be surpassed by Nvidia's inference-optimized Rubin
15.Leanstral 1.5: Proof abundance for all(mistral.ai)
370 points by programLyrique 49 days ago | 103 comments | permalink
tl;dr: Leanstral 1.5 is an Apache-2.0 licensed model (119B total/6B active params) for Lean 4 proof engineering that saturates miniF2F, solves 587/672 PutnamBench problems at ~$4 each (vs. ~$300 for Seed-Prover), and sets SOTA on FATE-H/X. Trained via mid-training, SFT, and RL with CISPO across theorem-proving and code-agent environments, it also demonstrated real-world utility by uncovering 5 previously unknown bugs across 57 open-source repositories. Weights are on Hugging Face with a free API endpoint available.
HN Discussion:
  • Mistral's focus on efficient specialized models is valuable even if not frontier-competitive
  • The highlighted bug-finding example is unimpressive as testing would catch such boundary conditions
  • Benchmark comparisons use outdated competitor models, making claims less impressive
  • Questioning why Lean 4 was chosen over other formal verification tools like Isabelle/HOL or TLA+
  • Curious whether the tool is accessible to newcomers without formal verification background
16.Half-Baked Product(weli.dev)
1370 points by weli 50 days ago | 403 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • Founders motivated by wealth rather than domain expertise cause mismatched expectations and failure
  • Satirical parody reinforcing the article's critique of overpromising startups
  • The core problem is disconnect between roles, each expert oblivious to other domains
  • ~The story is timeless and relatable, though the salesperson's perspective deserves more exploration
  • Personal anecdotes confirming the article's depiction of dysfunctional sales and VC dynamics
17.Android Developer Verification: Threat masquerading as protection(f-droid.org)
1718 points by drewfax 51 days ago | 737 comments | permalink
tl;dr: F-Droid argues that Google's upcoming Android Developer Verification (ADV) program—rolling out September 30 in Brazil, Indonesia, Singapore, and Thailand—is a preinstalled system service that will block installation of apps from developers not centrally registered with Google. They contend the anti-malware justification is a pretext, since the Developer Console ToS lets Google define "malware" arbitrarily (potentially targeting ad blockers or F-Droid itself), effectively ending 18 years of open Android software distribution. Despite widespread opposition from EFF, FSF, ACLU and 70+ organizations, regulators have been unresponsive, and key questions about how existing sideloaded apps will be affected remain unanswered.
HN Discussion:
  • Users should migrate to alternative Linux-based mobile OSes or GrapheneOS to escape Google control
  • The article's tone is childish and undermines F-Droid's credibility with reputable outlets
  • Phone ownership means the right to install anything without forced Google protection
  • Restricting to signed/permitted software threatens freedom and enables authoritarianism
  • Regulators, especially the EU, should intervene against this monopolistic overreach
18.Jamesob's guide to running SOTA LLMs locally(github.com)
405 points by livestyle 49 days ago | 182 comments | permalink
tl;dr: A detailed hardware guide for running SOTA LLMs locally, ranging from a $2k dual RTX 3090 setup (running Qwen3.6-27B and Whisper STT) to a $40k rig with 4x RTX Pro 6000s (384GB VRAM) capable of running GLM-5.2-594B at near-Claude-Opus quality. The author details their EPYC-based DDR4 build using c-payne PCIe4 switches for direct GPU-to-GPU communication, along with the finicky BIOS tweaks, ACS disabling, and kernel parameters needed to achieve Gen4 line-rate P2P (27.5 GB/s). Includes ready-to-run Docker configs and notes on power-limiting GPUs to run on a 110V circuit.
HN Discussion:
  • The $40k build cost is understated and local models still underperform cloud offerings
  • Cloud subscriptions or Macbooks are more cost-effective than expensive local rigs
  • ~Cheaper or middle-ground alternatives (single 3090, Arc B70, EVO-X2) offer better value than the recommended builds
  • Skepticism about quantized/pruned model quality claims approaching Claude Opus
  • Questions and additions about specific technical details like STT models and isolation