Jul 9Friday, July 10, 2026 · all daysJul 11 · today »
1.GPT-5.6(openai.com)
1549 points by logickkk1 63 days ago | 1101 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • Highlights useful developer guidance and semantic tips from the new model documentation
  • Mocks benchmark comparisons as cherry-picked or unfair to competitors like Fable
  • Notes impressive benchmark achievements like SOTA on ARC-AGI-3
  • Criticizes the confusing naming convention of Sol/Terra/Luna variants
  • ~Mixed real-world testing results suggest improvements are less dramatic than claimed
2.Show HN: Getting GLM 5.2 running on my slow computer(github.com)
922 points by vforno 63 days ago | 238 comments | permalink
tl;dr: Colibrì is a dependency-free C engine that runs GLM-5.2 (744B-parameter MoE) on modest hardware (~25GB RAM, 12 cores) by keeping the ~17B dense parameters resident in int4 while streaming the 21,504 routed experts from disk (~370GB) via an LRU cache. It implements MLA attention, MTP speculative decoding, DSA sparse attention, and an OpenAI-compatible API, achieving ~0.05–0.1 tok/s on the author's WSL2 dev box, with community benchmarks reaching ~2 tok/s on an M5 Max and ~1 tok/s on a 430GB EPYC system. Performance scales with RAM (cache size), disk bandwidth, and matmul throughput.
HN Discussion:
  • The README appears AI-generated based on repeated use of 'honest' phrasing
  • The reported tok/s is too slow to be practically useful even for overnight tasks
  • Others are working on similar streaming/LRU weight approaches and share their parallel efforts
  • This points toward a future where fast SSDs replace expensive RAM for LLM inference
  • ~Questions whether this offers advantages over llama.cpp's existing mmap and quantization support
3.EU Parliament greenlights Chat Control 1.0(patrick-breyer.de)
1624 points by rapnie 63 days ago | 853 comments | permalink
tl;dr: The EU Parliament failed to block "Chat Control 1.0" — a motion to reject it got 314 votes to 276 but fell short of the required 361-vote absolute majority — allowing suspicionless scanning of private messages on platforms like Gmail, iCloud, Instagram, and Discord to continue until 2028. End-to-end encrypted services like WhatsApp remain exempt. Critics, including former MEP Patrick Breyer and abuse survivors, argue the scanning is ineffective (48% of alerts aren't criminally relevant per Germany's BKA) and removes pressure to negotiate a targeted permanent regulation ("Chat Control 2.0"), talks on which resume in September.
HN Discussion:
  • EU is undemocratic, using procedural tricks to pass unpopular surveillance legislation
  • This vote destroys the EU's credibility on digital privacy and human rights
  • Disillusionment with EU as a democratic institution after this betrayal
  • Historical/constitutional parallels justify opposing such mass surveillance laws
  • Nuanced clarification that E2E encrypted services remain exempt from scanning
4.Train sim created by just one person is being called the best ever made(kotaku.com)
851 points by oumua_don17 67 days ago | 346 comments | permalink
tl;dr: Running Train, an Early Access train sim built by solo developer Novatetsu Games, is drawing rave Steam reviews for its meticulously detailed fictional Japanese setting—40km of track with logically placed powerlines, traffic, temples, and dynamic weather/seasons. It offers 42 routes across two fake rail lines, supports the Zuiki MASCON peripheral, and can be played hands-on or set to auto-drive while you explore via free camera. It's $18, with plans to expand to 100km of track and add passengers and a conductor mode by end of next year.
HN Discussion:
  • Amazement at solo dev achievement enabled by free modern tools like Unreal Engine
  • Skepticism that the game is as impressive as claimed, calling it repetitive tech demo
  • Criticism of the article's quality and journalist not actually playing the game
  • Questions about asset sourcing and how a solo dev achieves this quality
  • ~Contextualizing the game as derivative of existing train sims like Densha de go
5.Show HN: 18 Words(18words.com)
1143 points by pompomsheep 63 days ago | 357 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • ~The timer detracts from enjoyment; a relaxed/untimed mode would improve the experience
  • ~Players should progress through all 18 words with a cumulative score rather than losing early
  • A shuffle/scramble button would help players break out of mental locks on letter pairings
  • The game has bugs or unfair word choices, like rejecting valid anagrams or using obscure slang
  • The game reveals interesting cognitive/linguistic patterns, especially for non-native speakers
6.Postgres rewritten in Rust, now passing 100% of the Postgres regression tests(github.com)
788 points by SweetSoftPillow 63 days ago | 705 comments | permalink
tl;dr: pgrust is a Rust rewrite of Postgres targeting 18.3 compatibility, now passing all ~46,000 regression tests and able to boot from an existing Postgres data directory. An unreleased in-progress version reportedly uses threads instead of processes, runs 50% faster on transactional workloads, and ~300x faster on analytical workloads (within 2x of ClickHouse on ClickBench). It's not production-ready, lacks extension support (PL/Python, PL/Perl, etc.), and is AGPL-3.0 licensed.
HN Discussion:
  • Author explains project is an LLM-driven experiment to rearchitect Postgres
  • Skepticism about single-person LLM-generated rewrites lacking long-term viability
  • Tests alone don't prove reliability; production battle-scars matter more
  • Heavy use of unsafe Rust suggests mere AI transpilation, not a true rewrite
  • ~Licensing concerns about AGPL relicensing and potential violations of original license
7.Interview with Mitchell Hashimoto about Ghostty and Zig(alexalejandre.com)
377 points by veqq 62 days ago | 226 comments | permalink
tl;dr: Mitchell Hashimoto (of HashiCorp fame) discusses building Ghostty to sharpen his skills in GPU programming, systems programming, and Zig, arguing terminals need better foundational protocols (like an n-screen API and button protocol) rather than becoming full app platforms. He defends a "feature-rich but not bloated" philosophy, pushes back on user entitlement in open source (telling people to fork), and praises Zig's willingness to make breaking changes—noting AI tooling makes such migrations far less painful. He also argues learning C matters less than understanding how computers actually work at the syscall level.
HN Discussion:
  • Admiration for Mitchell's thoughtful, pragmatic approach and philosophy expressed in the interview
  • Forking is not as simple as suggested due to maintenance burden of syncing with upstream
  • ~Rust culture criticism may be based on skewed external interactions rather than the actual community
  • Zig culture has similar off-putting behavior, ironically mirroring the Rust criticism
  • Disagreement with praise for PowerShell's structured data; CLI tools should default to plain text
8.Hy3(hy.tencent.com)
545 points by andai 63 days ago | 114 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • Shares testing experiences and free tier availability info on Hy3
  • Hy3 is uncompetitive against DeepSeek V4 and GLM-5.2 on price/performance
  • Hy3 is impressively capable for its size and could be a good local model
  • Hy3 is overhyped or benchmark-gamed and disappointing in practice
  • Broader commentary on LLM market tiers and need for architectural breakthroughs
9.The glass backbone: Why the Army's logistics will break in the next war(mwi.westpoint.edu)
452 points by baud147258 63 days ago | 644 comments | permalink
tl;dr: The US Army's logistics system, optimized for permissive counterinsurgency environments with large static bases and uncontested supply lines, is dangerously vulnerable in a peer conflict where drones, precision fires, and pervasive sensing have eliminated the safe rear area—as demonstrated by Russian convoy failures in Ukraine. The author argues the Army must shift from centralized hub-and-spoke sustainment to dispersed, mobile, signature-managed nodes with organic air defense, up-armored vehicles, and autonomous resupply platforms. Most critically, sustainment must be elevated culturally and budgetarily to a primary warfighting function, since in industrial warfare the logistical "tail" is now the enemy's primary target.
HN Discussion:
  • Article is insightful and correctly identifies logistics as the core warfighting priority
  • ~This concern is cyclical and the military pendulum swings between logistics focus and cutting support roles
  • Over-optimized systems become fragile when conditions change, supporting the article's core vulnerability thesis
  • Article underestimates US industrial base capabilities in drones and logistics mass movement
  • ~New technologies like space-based delivery and drones will reshape the logistics vulnerability equation
10.No leap second will be introduced at the end of December 2026(datacenter.iers.org)
307 points by ChrisArchitect 63 days ago | 243 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • Curiosity about what causes unpredictability in Earth's rotation requiring leap second adjustments
  • Concern about how leap seconds (or lack thereof) impact software systems like UNIX timestamps and Spanner
  • Support for abandoning leap seconds since they cause too much computing trouble and drift is negligible
  • Appreciation and humor about the formal language and authorities involved in timekeeping
  • Technical clarification about UTC-TAI-GPS offset relationships and questions about the 2017 reference
11.A road to Lisp: Why Lisp(scotto.me)
288 points by silcoon 63 days ago | 294 comments | permalink
tl;dr: Lisp's power comes from the combination of homoiconicity (code-as-data), macros that let you extend the language itself, and a live REPL-driven development environment where you continuously evaluate and redefine code in a running process. These features enable programmers to build domain-specific languages tailored to their problem, and make software inherently extensible—users can leverage the same DSLs the developer used internally, as seen in AutoCAD's AutoLISP and Emacs. Though Lisp never became mainstream, learning it fundamentally changes how you think about programming.
HN Discussion:
  • ~Programming languages balance restricting programmers vs empowering them; Lisp represents the powerful 'Dark Side'
  • Lisp tooling continues to improve with new editors and REPLs available today
  • Lisp articles are one-sided propaganda that lack level-headed criticism or objective analysis
  • The article overstates uniqueness of REPLs and hot-reloading which are common in other languages now
  • Working with Lisp reveals how other mainstream languages hinder programmers, validating its virtues
12.A possible future for Damn Interesting(damninteresting.com)
314 points by mzur 63 days ago | 44 comments | permalink
tl;dr: Alan Bellows, founder of Damn Interesting, is running a one-off GoFundMe to replace the part-time engineering income he used to subsidize the site with, after being forced into a full-time job that's left him unable to produce content. The goal is to buy back roughly a year of his time to write long-form articles as a counter to the flood of AI-generated content. He notes this is separate from the site's existing "Give a Damn" donation system that covers operational expenses.
HN Discussion:
  • Longtime readers expressing nostalgia and donating to support the site
  • Praise for DI's influence on the broader 'interesting content' genre and podcasting
  • ~Suggestion to adopt alternative monetization models like Patreon with tiers
  • Broader analysis of how the creator economy model for long-form text has broken down
  • Author clarifies he didn't self-promote the post to HN
13.Muse Spark 1.1(ai.meta.com)
400 points by ot 63 days ago | 209 comments | permalink
tl;dr: Meta Superintelligence Labs released Muse Spark 1.1, a multimodal reasoning model with a 1M-token context window, improved agentic capabilities, computer use, and coding performance, including multi-agent orchestration and script/click automation. It's available via the new Meta Model API (public preview), in the Meta AI app, and on meta.ai, with early adoption from Replit, Cline, and Box.
HN Discussion:
  • Benchmark results are questionable due to violating standard resource constraints
  • Aggressive pricing makes this a compelling commodity coding model option
  • Meta's strategy of commoditizing frontier models is smart and disruptive to competitors
  • More competition among AI labs benefits consumers and developers
  • Missing data retention policies and lack of OpenRouter availability hinder adoption
14.Why American ambulance rides are so expensive(davidoks.blog)
307 points by jyunwai 62 days ago | 451 comments | permalink
tl;dr: American ambulance bills are extreme because a 1965 Medicare decision treats ambulance service as a per-ride procedure, but modern EMS costs are almost entirely fixed—paying crews and vehicles to stand ready 24/7. Since Medicare, Medicaid, and the uninsured all pay below cost, and insurers have no incentive to go in-network (ambulances can't steer patients), providers recover their costs via massive out-of-network surprise bills to the privately insured. The fix is funding readiness like an option—via taxes or premiums—as other wealthy countries do.
HN Discussion:
  • Billing practices inflate charges through medical coding to maximize settlements
  • Other countries handle ambulance costs far more reasonably than the US
  • The article misunderstands private equity's role in extracting profits
  • ~The article's options analogy is unnecessary and overcomplicated for a simple explanation
  • Practical advice on refusing rides or disputing bills to avoid charges
15.John Deere owners will get the right to repair equipment under FTC settlement(apnews.com)
1386 points by djoldman 63 days ago | 302 comments | permalink
tl;dr: John Deere has settled with the FTC and five state attorneys general, agreeing to provide diagnostic and repair tools to equipment owners and independent shops rather than restricting them to authorized dealers. The company will pay $1 million to the states, face 10 years of compliance oversight, and is barred from retaliating against those who bypass its dealer network. This follows a separate $99 million class-action settlement Deere reached with farmers in April.
HN Discussion:
  • ~Fine is trivially small and won't deter John Deere's anti-consumer behavior
  • Settlement contains loopholes and bureaucratic delays that undermine real repair rights
  • Right to repair is a fundamental freedom, not something to be negotiated in settlements
  • Positive step that should extend to other industries like automobiles
  • Credit to activists like Louis Rossmann for pushing right-to-repair forward
16.Buried Apple feature turns an iPhone into the perfect kids' dumb phone(wired.com)
377 points by PotatoNinja 66 days ago | 252 comments | permalink
tl;dr: Apple's Assistive Access mode (buried in Settings > Accessibility, introduced in iOS 17 for users with cognitive disabilities) can transform an old iPhone into a customizable "dumb phone" for kids, with large-tile UI, whitelisted apps, and—unlike Screen Time restrictions—a hard block on web browsing that can't be bypassed via messaged links. The author configured his son's iPhone 13 with just Calls, Messages, Maps, Camera, Photos, and Music, retaining Find My tracking without monthly fees. Downsides: it runs sluggishly, disables voicemail, prevents powering off, and occasionally freezes (e.g., in Messages emoji search).
HN Discussion:
  • Accessibility features benefiting broader users exemplifies the curb cut effect
  • ~MDM via Apple Configurator is a more effective restriction alternative
  • Feature has significant limitations like no third-party apps, making it unsuitable for elderly users
  • Feature is too slow and restricts contacts too much for practical dumb phone use
  • Author's parenting choices (blocking selfies, assumptions about needing a smartphone) are questionable
17.GLM 5.2 is nearly as accurate as a human book keeper(toot-books.pages.dev)
220 points by adamkurkiewicz 62 days ago | 118 comments | permalink
tl;dr: GLM 5.2, an open-weights model, prepared a quarterly UK VAT return for a small business (59 transactions) in 68 minutes at a token cost of $2.73, with the net VAT position off by just 7 pence from the human-prepared ground truth. Out of 354 scored checks, it failed 20, with only one serious error (misclassifying £10,000 in founder share capital); most other mistakes involved confusing zero-rated with tax-exempt VAT categories. The authors argue bookkeeping is becoming a solved problem and are building tooling (toot-books.com) to deploy this to UK SMEs.
HN Discussion:
  • Benchmark is unfair because humans did broader work like sourcing invoices while the LLM got pre-packaged context
  • Legal liability and accountability concerns make LLM bookkeeping risky since responsibility falls on the user
  • Skeptical of trusting an unknown startup with sensitive financial data despite the results
  • Bookkeeping is a well-constrained problem that LLMs can handle reliably, confirming the article's thesis
  • 'Essentially correct' isn't good enough for tax authorities, and the remaining errors are concerning
18.AI content is everywhere on social media, especially LinkedIn(pangram.com)
237 points by mukmuk 63 days ago | 214 comments | permalink
tl;dr: Pangram's Chrome extension analyzed over 1 million social media posts and found that 25% of longform content (250+ words) is fully AI-generated, with LinkedIn accounting for two-thirds of all flagged AI content and over 40% of its longform posts. X/Twitter had the highest combined AI rate at nearly 47% when including mixed human/AI writing, while Reddit stayed low overall (4.4%) due to mostly human-written replies—though top-level Reddit posts were 5x more likely to be AI than comments.
HN Discussion:
  • Writing with AI destroys authentic voice and personal connection in communication
  • Retreating from algorithmic social feeds to RSS/webrings as a response to AI slop
  • Skepticism about Pangram's claimed 99.98% AI detection accuracy
  • ~LinkedIn was always full of scripted BS; AI just accelerated an existing trend
  • LinkedIn has become useless, justifying deletion and skepticism of its professional value
19.ChatGPT Work(openai.com)
348 points by Tiberium 63 days ago | 184 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • The unification and rebranding is confusing, with unclear differences between modes
  • Regression in UX by relegating casual chat to a tiny window and renaming to 'Classic'
  • Unification was overdue and follows Anthropic's better-executed approach
  • Hosted long-running agents for enterprise work are the future direction
  • Neutral observations about specific feature differences like effort levels or use cases
20.Meta reuses old RAM in new servers with custom bridge chip(theregister.com)
326 points by ihsw 68 days ago | 228 comments | permalink
tl;dr: Meta built a custom CXL 2.0 ASIC called "Vistara" to repurpose DDR4 DIMMs from decommissioned servers into new DDR5-based "MemServer" machines, exposing the older memory as a CPU-less NUMA node via tweaked Linux kernel drivers. The approach sidesteps off-the-shelf CXL limitations (no DDR4 support, bundled DRAM, high cost) and is already running across millions of servers. Meta claims a 25% server reduction for disaggregated ML inference workloads and a 33% drop in OOM-related job failures.
HN Discussion:
  • Speculates that RAM scarcity may return, echoing sci-fi predictions of memory as valuable commodity
  • Questions novelty since off-the-shelf CXL memory expander chips already exist
  • Title overstates significance; it's a niche application of existing CXL standard with latency tradeoffs
  • Wishes a similar consumer-level solution existed for reusing old RAM
  • Concerned about consumer impact from RAM shortages and rising electronics prices