Jul 9Friday, July 10, 2026 · all days
1.GPT-5.6(openai.com)
1342 points by logickkk1 18 hours ago | 934 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • Highlights useful semantic tips and benchmark achievements from the model's documentation
  • Skeptical of benchmark comparisons being cherry-picked or exclusions being convenient
  • Confused or frustrated by the naming convention (Sol/Terra/Luna) and model selection
  • ~Independent testing shows model is comparable but not superior to competitors like Sonnet 5
  • Appreciates the focus on token efficiency alongside intelligence improvements
2.Show HN: Getting GLM 5.2 running on my slow computer(github.com)
729 points by vforno 1 day ago | 179 comments | permalink
tl;dr: A developer built "colibrì," a dependency-free C engine that runs the 744B-parameter GLM-5.2 MoE model on consumer hardware (~25GB RAM) by keeping the dense weights (~10GB int4) resident and streaming the 370GB of routed experts from NVMe on demand, with an LRU cache and MTP speculative decoding. Performance is disk-bound: ~0.05–0.1 tok/s on the author's WSL2 machine, but community benchmarks show ~1 tok/s on an M5 Max and projections of 5–15 tok/s on beefier hardware. Includes an OpenAI-compatible API and optional CUDA backend for pinned hot experts.
HN Discussion:
  • Suspicion that the project's writeup is AI-generated based on stylistic tells like overuse of 'honest'
  • ~Questioning practical usability given the extremely low tokens/second performance reported
  • Excitement about similar streaming/offloading approaches and sharing parallel projects
  • Optimism that SSD streaming could replace expensive RAM as a viable architecture for local LLMs
  • Skepticism that this offers real gains over existing solutions like llama.cpp's mmap approach
3.EU Parliament greenlights Chat Control 1.0(patrick-breyer.de)
1446 points by rapnie 1 day ago | 702 comments | permalink
tl;dr: The EU Parliament failed to block "Chat Control 1.0" after a rejection motion fell short of the required absolute majority (314-276 against, but needed 361), reinstating suspicionless scanning of private messages on US platforms like Gmail, Instagram, and Discord until 2028. End-to-end encrypted services like WhatsApp remain exempt, and critics argue the mass scanning is ineffective—99% of Meta's reports involve previously known material, and 48% of alerts aren't criminally relevant. Negotiations over a permanent "Chat Control 2.0" regulation resume in September.
HN Discussion:
  • EU procedural manipulation exposes it as undemocratic and heading toward totalitarianism
  • This legislation undermines EU credibility on privacy and digital rights
  • Users should adopt privacy tech like Tor, VPNs, and Signal to evade surveillance
  • This mirrors historical tyranny that justified constitutional protections like the US 4th Amendment
  • Member states use EU as blame-laundering mechanism for unpopular domestic laws
4.Train sim created by just one person is being called the best ever made(kotaku.com)
655 points by oumua_don17 5 days ago | 249 comments | permalink
tl;dr: Running Train, an Early Access train sim built by solo developer Novatetsu Games, recreates a fictional Japanese region with 42 routes across 40km of meticulously detailed track—including logically placed powerlines, traffic, and weather/seasonal effects—much of which isn't even visible from the driver's cab. Steam reviews are overwhelmingly positive, praising the modeling, lighting, and support for the Zuiki MASCON peripheral. Planned additions include passengers, a conductor mode, and expansion to 100km of track by end of next year. It's available now for $18.
HN Discussion:
  • Amazement that a single developer could create such a polished, photorealistic game
  • Curiosity about how a solo dev sources or creates so many high-quality assets
  • Appreciation for modern tools like free Unreal Engine enabling solo devs from anywhere
  • Criticism that the article is shallow and the journalist didn't actually play the game
  • Skepticism about the 'best ever' framing, noting it's derivative of Densha de Go
5.Show HN: 18 Words(18words.com)
1019 points by pompomsheep 23 hours ago | 329 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • Author engages with community, asking for and implementing feedback on game features
  • ~The timer detracts from enjoyment; a relaxed/untimed mode would be preferable
  • ~Game should continue through all 18 words with a final score rather than ending on failure
  • ~A shuffle/scramble button would help players get unstuck on difficult words
  • Word validation bugs and questionable word choices (like accepting Scottish slang or rejecting valid anagrams) hurt the experience
6.Postgres rewritten in Rust, now passing 100% of the Postgres regression tests(github.com)
709 points by SweetSoftPillow 1 day ago | 598 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)
274 points by veqq 18 hours ago | 131 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)
499 points by andai 20 hours ago | 103 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)
392 points by baud147258 22 hours ago | 505 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)
291 points by ChrisArchitect 21 hours ago | 225 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)
249 points by silcoon 22 hours ago | 195 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)
291 points by mzur 20 hours ago | 40 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)
384 points by ot 21 hours ago | 190 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)
239 points by jyunwai 13 hours ago | 332 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)
1333 points by djoldman 1 day ago | 284 comments | permalink
tl;dr: The FTC and five state AGs reached a settlement with John Deere requiring the company to provide diagnostic and repair software to equipment owners and independent shops, ending its practice of restricting repairs to authorized dealers. Deere must also pay $1 million to the states, faces 10 years of compliance oversight, and is barred from allowing dealer retaliation against those who repair their own equipment. This follows a separate $99 million class-action settlement with farmers in April.
HN Discussion:
  • Credits activists like Louis Rossmann for advancing right-to-repair advocacy
  • ~Right to repair should be a fundamental right, not a negotiated settlement
  • ~The $1 million fine is far too small to deter a company of Deere's size
  • Settlement contains loopholes allowing Deere to stall compliance through bureaucracy
  • This precedent should extend to other locked-down industries like cars, printers, and Cricut
16.Buried Apple feature turns an iPhone into the perfect kids' dumb phone(wired.com)
352 points by PotatoNinja 4 days ago | 225 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)
208 points by adamkurkiewicz 17 hours ago | 116 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)
220 points by mukmuk 20 hours ago | 200 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)
341 points by Tiberium 18 hours ago | 174 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)
316 points by ihsw 6 days ago | 224 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