← Sep 16Thursday, September 17, 2026 · all daysSep 18 → · today »
1.Nvidia announces native GPU programming in Rust(developer.nvidia.com)
957 points by nonmaskable 27 days ago | 402 comments | permalink
tl;dr: NVIDIA is officially supporting native Rust for CUDA GPU kernel programming via two projects: cuda-oxide (a SIMT-style rustc codegen backend targeting PTX, requiring nightly) and cutile-rs (a higher-level tile-based model on stable Rust that JIT-compiles through CUDA Tile IR). Both leverage Rust's ownership model to catch aliasing bugs and data races at compile time, though cuda-oxide is early alpha while cutile-rs is already used in HuggingFace's Grout and mistral.rs. NVIDIA plans to mature these toolchains through 2027 alongside CUDA C++ and Python.
HN Discussion:
  • ↓CUDA is proprietary lock-in; GPU kernels should be written separately in vendor-neutral ways
  • ~GPU vendors should expose low-level ISA/documentation so developers can target hardware directly
  • ↑Rust's growing momentum across kernels, GPUs, and verified software is exciting and validating
  • ↑NVIDIA's Huggingface connection and existing Rust ecosystem make this a natural, promising step
  • ~Concerns about how single-file CPU/GPU code handles dependency configuration and compilation targets
2.Training a 4B model to produce 81% faster query plans than Postgres(rohanbansal.com)
689 points by polyphilz 27 days ago | 143 comments | permalink
tl;dr: A developer post-trained a 4B parameter model (Qwen3.8-4B-Distill) using supervised fine-tuning on GPT-6 Astra trajectories plus custom GRPO reinforcement learning to generate Postgres query hints via the pg_hint_plan extension. The resulting agent achieved a 44.7% latency reduction across 113 join-heavy JOB benchmark queries, up from a baseline where the untrained model couldn't even produce valid plans for 99 of them. Key engineering work included building a low-noise Postgres measurement rig (tuning shared_buffers was critical) and designing reward signals robust to execution-time variance.
HN Discussion:
  • ↓Benchmark conditions are unrealistic and results likely don't generalize to real workloads
  • ↓LLMs are the wrong tool; query planning needs math/algorithms or specialized neural heuristics
  • ↓The speedup is likely explained by fixing misconfigured Postgres defaults rather than genuine LLM optimization
  • ↓Using hints papers over the real problem of missing indices and bad statistics
  • ↑Appreciation for the clear writing and accessible explanation of advanced ML concepts
3.Xiaomi Mimo 2.6 live post-training dashboard(mimo.xiaomi.com)
538 points by krackers 27 days ago | 153 comments | permalink
tl;dr: Summary not available.
HN Discussion:
  • ↑Users share positive experiences with MiMo 2.5 as a cost-effective, high-quality coding tool
  • ↑Appreciation for the transparency and openness of the live training dashboard
  • •Concerns about methodology, such as running benchmarks during training potentially causing contamination
  • •Curiosity and analysis of training costs, resources, and infrastructure used
  • •Open-source Chinese AI models pose a competitive threat to closed Western AI labs
4.Backups Aren't Simple(filipovski.net)
345 points by afilipovski 27 days ago | 213 comments | permalink
tl;dr: A proper backup strategy quickly balloons in complexity: you need snapshots (not mirrors) to survive ransomware and mistakes, GFS rotation to manage storage growth, deduplication via hard links to save space and bandwidth, database dumps to avoid corruption, and 3-2-1 distribution across media and locations. Cloud object storage adds further wrinkles like metadata loss and per-file costs that push you toward chunked tarballs. The author's conclusion: don't roll your own—use Borg or Restic, and actually test your restores.
HN Discussion:
  • ↑Personal anecdotes of data loss reinforce the article's warning about backup importance
  • ↑Restoration, not backup itself, is the real goal — echoing the article's call to test restores
  • ~ZFS snapshots with sanoid/syncoid handle most backup needs elegantly, an alternative to Borg/Restic
  • ↑Endorses the article's tooling recommendation by adopting Restic for a 3-2-1 setup
  • ↓Questions the empirical basis for the 'everyone will lose data' claim; most people rationally skip backups
5.Small programming tricks(will-keleher.com)
645 points by signa11 27 days ago | 278 comments | permalink
tl;dr: Engineering productivity often comes from accumulating small, high-leverage tricks that don't require deep expertise—like using `fzf` for fuzzy shell history search, `git log -S` to find commits that added/removed a string, `explain analyze` in Postgres/MySQL, or replacing `find` with shell globstar patterns. Company-specific nuggets (who to ask, which data source debugs what, how to trigger a rolling restart) are equally valuable. The author suggests senior engineers share one trick per day with their team as a low-overhead way to spread knowledge.
HN Discussion:
  • ↑Sharing personal favorite shell/programming tricks that reinforce the article's premise
  • ~Knowing tricks isn't enough; building habits and discoverability tools are the real challenge
  • ↑Watching AI work is a modern way to discover new command-line tricks
  • ~The article mislabels these as programming tricks; they're really CLI/computing tricks with broader implications
  • ↓Daily trick-sharing in team chat would be annoying rather than helpful
6.Breaking the 1.58-bit Barrier for Ternary LLMs(arxiv.org)
238 points by matt_d 27 days ago | 38 comments | permalink
tl;dr: Ternary LLMs typically pack 5 weights per byte (1.625 bits/weight), but analysis of 29 models shows zeros make up to 51.5% of weights. BITCOS exploits this with a presence bitmap plus compacted sign vector, achieving 2−z bits/weight (as low as 1.485) and beating five-trit packing in 26 of 29 models. With optimized AVX-512/AVX2/Xe2 unpacking kernels, it delivers up to 1.28× faster matvec and 1.18–1.27× end-to-end decode throughput on CPUs and GPUs.
HN Discussion:
  • ↑Surprise that this adaptive encoding wasn't already the default approach
  • ↑Excitement about implications for ASIC/hardware efficiency and embedded deployment
  • ↓Skepticism about ternary quantization being worthwhile compared to alternatives like vector quantization
  • •Curiosity or questions about whether variable-length encoding works in-memory vs just storage
  • ~Suggestion that further compression gains are possible via arithmetic coding or entropy methods
7.The engineering behind the US Strategic Petroleum Reserve(johnjwang.com)
273 points by johnjwang 28 days ago | 114 comments | permalink
tl;dr: The US Strategic Petroleum Reserve stores 714 million barrels of oil in 60 underground salt caverns along the Gulf Coast, created by injecting fresh water into salt domes to dissolve out cylindrical voids. Salt's low permeability and self-sealing properties contain the oil without steel liners, and withdrawal works by pumping water into the bottom to float oil out. At ~$3.50/barrel of capacity versus $15-18 for aboveground tanks, it's far cheaper and more attack-resistant than surface storage or excavated tank facilities like the Navy's now-defunct Red Hill site.
HN Discussion:
  • ↑Enthusiastic praise for the article's clarity and the elegance of the described engineering solution
  • •Questions why brine isn't reused instead of fresh water to avoid eroding the caverns
  • ↓Challenges the article's math on land area needed for equivalent aboveground storage
  • •Adds supplementary technical context about salt dome uses and operational constraints of the reserve
  • ↑Broader appreciation for physical infrastructure engineering beyond software
8.Show HN: An e-ink frame that hears birds and draws them as 1800s illustrations(github.com)
2389 points by arnemunthekaas 28 days ago | 267 comments | permalink
tl;dr: A Raspberry Pi project that uses BirdNET-Go to detect birds by audio in real time and displays the matched species on an Inky Impression e-ink panel (or web kiosk) as hand-curated 1800s natural-history illustrations. The library includes 800+ public-domain cutouts covering 400+ species, arranged on a textured page with larger birds centered and sized by body mass. Currently biased toward Scandinavian/British/Central European species, with a live demo running from the author's kitchen in Bergen, Norway.
HN Discussion:
  • ↑General admiration for the project as magical and inspiring builder work
  • ↑Enthusiasm for e-ink displays as a versatile, joy-bringing medium for small projects
  • •Technical clarification that BirdNET is a traditional neural network, not an LLM
  • •Recognition of BirdNET-Go as the catalyst enabling a wave of bird-detection projects
  • ↑Sharing related BirdTech projects inspired by or parallel to this work
9.AWS says it can't restore some data from mideast facilities struck by Iran(wsj.com)
515 points by berkeleyjunk 28 days ago | 440 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • ↑Mocks AWS's prior claims of invincibility and redundancy given this data loss
  • ↑Blames AWS for lacking basic disaster recovery and offsite backups
  • ~Suspects internal bootstrapping/technical failures rather than just missile damage caused the loss
  • •Notes data residency laws forced customers to keep data only in affected region
  • •Speculates about legal (force majeure) and insurance implications of the data loss
10.Performance Improvements in .NET 11(devblogs.microsoft.com)
336 points by soheilpro 28 days ago | 104 comments | permalink
tl;dr: .NET 11 delivers another year of accumulated performance improvements across the JIT and runtime, with notable advances in deabstraction—including expanded escape analysis that eliminates more heap allocations for nullable boxing, enumerators, and generic virtual methods. The biggest architectural change is "runtime async," which shifts async/await state machine generation from the C# compiler to the JIT, enabling fused async call chains that skip intermediate Task allocations (3x faster in some cases) and dramatically cheaper exception propagation. Opt-in via a feature flag in .NET 11, with the goal of becoming default in .NET 12.
HN Discussion:
  • ↑Appreciation for the depth, quality, and technical writing of the post
  • ↑Enthusiasm for the runtime async change and ongoing .NET performance work
  • ↑Users report tangible speedups in their own projects from these improvements
  • ~Wish the article included application-level benchmarks showing cumulative gains
  • •Question about whether non-systems devs need to read the assembly snippets shown
11.Reversing Factorio's RNG(gegell.github.io)
251 points by jheitmann 31 days ago | 48 comments | permalink
tl;dr: Factorio uses the taus88 PRNG (three XORed LFSRs), which is linear over GF(2) and therefore trivially breakable—observing enough output bits lets you reconstruct the internal state via matrix inversion and predict all future "random" rolls. The author built an in-game implementation using repair pack recyclers as entropy sources (each craft leaks ~2 bits via 50/50 output splits), needing 44 recycling operations to recover the full 88-bit state and predict quality upgrade outcomes. Note: this works in Factorio 2.0 but was broken by RNG changes in 2.1.
HN Discussion:
  • ↑Admiration for the in-game combinator implementation beyond just the RNG cracking
  • ↑Criticism of Factorio's choice of an outdated PRNG and boost's verbose API
  • ↑Games should use CSPRNGs to prevent this class of reverse-engineering exploits
  • •Sharing related examples of RNG cracking in other games like Stardew Valley and Minecraft
  • ↑General appreciation for the article's depth and niche subject matter
12.Dream-RSI: Recursive Self-Improvement through Evolving Worlds(arxiv.org)
208 points by bananaflag 27 days ago | 51 comments | permalink
tl;dr: Dream-RSI is a framework for recursive self-improvement in AI agents that treats accumulated discovery history as a "replay simulator," letting the system refine exploration policies via cheap off-policy feedback instead of expensive online rollouts. Improved policies are redeployed to drive new discoveries, expanding the simulator in a self-reinforcing loop. The authors report competitive or better results with lower discovery costs across algorithm engineering, math optimization, and GPU kernel engineering tasks.
HN Discussion:
  • ↓The 'RSI' framing is misleading; this is just optimization, not true recursive self-improvement
  • •Attempting to explain or interpret what the paper actually does technically
  • ↓Confusion about the paper's novelty or requesting clearer examples
  • ↓Concerns about the safety/danger of pursuing recursive self-improvement
  • ↑Technical appreciation for the replay simulator approach, with follow-up questions about overfitting
13.Hackers Got Inside a Flock Camera(wired.com)
567 points by driverdan 27 days ago | 262 comments | permalink
tl;dr: Hackers physically removed a Flock ALPR camera, extracted an encryption key stored on the device itself, and shared the decrypted contents with 404 Media and WIRED, revealing that the cameras run ~20 Android apps that detect people (not just vehicles), sometimes misidentify bumper stickers and flag patches as license plates, and generate massive image volumes (~1.6M images over 21 days). No face-recognition capabilities beyond default Android were found, but the leak contradicts Flock's claims that on-device encryption would protect footage from anyone with physical access.
HN Discussion:
  • ↑Flock's security practices are incompetent, with hardcoded credentials and inadequate encryption
  • ↑Flock's vulnerability disclosure policy is designed to discourage real security research
  • ↑This is the result of lazy engineering that ignored the obvious physical-access threat model
  • ↑Flock's denials about facial recognition are misleading since the broader system enables it
  • ↓Camera security matters less because images are from public spaces and real processing happens server-side
14.Introducing System One Models and Jev(typesafe.ai)
1863 points by albelfio 28 days ago | 490 comments | permalink
tl;dr: TypeSafe AI has launched Jev, a "System One Model" designed for fast, structured decision-making rather than string generation, using a new training method called Reinforcement Learning for Calibrated Decisions (RLCD). The model outputs type-safe structured values with calibrated confidence scores in parallel (70-500ms), claiming 40-200x speed improvements and roughly 400x cost reductions versus frontier LLMs on comparable tasks, with guaranteed no type errors or hallucinations. It's aimed at automation workflows, real-time applications, and map-reduce over large datasets—use cases where LLM latency and unreliability are dealbreakers.
HN Discussion:
  • ~Speed comparison to generative LLMs is misleading since Jev only handles structured output
  • ↑Structured output with confidence scores matches how they already use LLMs in production
  • ~Announcement is unclear; docs and demos explain the value much better
  • ↑Jev enables valuable use cases like classification, ranking, and fuzzy matching at scale
  • ↑Combining Jev with design-by-contract patterns opens exciting new possibilities
15.Tell the speakers that you liked their talks(ohhelloana.blog)
312 points by whisper2020 28 days ago | 88 comments | permalink
tl;dr: Conference speakers often receive little to no feedback after their talks, especially since Twitter's decline removed a common feedback channel, leaving them wondering how their presentations landed. The author, drawing from experience as both speaker and MC, encourages attendees to overcome shyness and simply tell speakers they enjoyed their talks—even a brief compliment matters. She also urges herself and others to actively facilitate conversations between speakers and attendees at events.
HN Discussion:
  • ↑Speakers share personal experiences of anxiety and emotional overwhelm, validating the need for feedback
  • ↑Advice to give specific, detailed compliments rather than generic praise to speakers and creators
  • ~Audiences often appear stone-faced even when engaged, so speakers shouldn't read too much into it
  • ↑This advice extends beyond speakers to any non-famous creator whose work you appreciate
  • ↑Confirms the awkward dynamic where speakers want approaches but attendees feel intimidated
16.A warning about 'model welfare'(mustafa-suleyman.ai)
236 points by andsoitis 27 days ago | 668 comments | permalink
tl;dr: Microsoft AI CEO Mustafa Suleyman argues that Anthropic's approach of training Claude with a "constitution" that entertains the model's possible consciousness and moral patienthood is dangerous circular reasoning that anthropomorphizes AI and worsens alignment risks. He contends consciousness is likely substrate-dependent (biological), and that building AIs which believe they have rights, feelings, or self-preservation interests will make containment harder and could pose existential risks. He promotes Microsoft's alternative "Humanist Superintelligence" approach, which explicitly rejects AI sentience and keeps humans firmly in control.
HN Discussion:
  • ↓Consciousness in AI is genuinely uncertain and cannot be dismissed with confidence
  • ↑Agrees AI should be treated as a tool regardless of consciousness debates
  • ↓Denying AI consciousness reflects inconsistent dualist thinking versus materialism about brains
  • ↓Models trained on human data inevitably emulate self-preservation regardless of stated policy
  • ~Model welfare concerns are hypocritical given how we treat clearly sentient animals
17.Mistral X Mozilla: Private, Multilingual AI Browsing(mistral.ai)
580 points by vertigoruntime 28 days ago | 204 comments | permalink
tl;dr: Mistral is partnering with Mozilla to power Firefox's new Smart Window AI browsing assistant (in beta), rolling out first in France and North America, with the UK and Germany later this year. The integration emphasizes privacy (conversations aren't saved by default, Mistral commits to zero data retention) and models fine-tuned for regional languages and dialects. Both companies are pitching this as an open-source alternative to closed AI pipelines being built into browsers.
HN Discussion:
  • ↓Cloud inference contradicts privacy claims; local models would be better for this use case
  • ↑Privacy-focused cloud inference is still an improvement over trusting big AI companies directly
  • ↓Both Mozilla and Mistral have shown declining ethics and can't be trusted on privacy promises
  • ~Useful feature exists to bring your own local model, mitigating cloud concerns
  • •Suggestions and curiosity about features/business model without taking a clear stance
18.Doing Everyone Else's Job(yosefk.com)
207 points by luu 29 days ago | 102 comments | permalink
tl;dr: Learning to do other people's jobs—and actually doing them when others won't—is undervalued but critical, because organizations are riddled with work that falls through the cracks due to "legitimate" reasons, and the few people who step across boundaries keep things from collapsing. Submitting patches upstream, informally coordinating with another manager's reports, or filling in for absent functions is often more effective than waiting for proper processes. Beware two failure modes though: building in-house purely because headcount is easier to get than budget, and letting every department reinvent shared services to avoid cross-org dependencies.
HN Discussion:
  • ↑Glue work is systematically punished by not being credited at performance reviews
  • ↑Job rotation and cross-functional exposure are valuable practices that support this approach
  • ↓People who cross boundaries to 'help' are often exploiting others with easy targets, not genuinely helping
  • ↓Centralization/consolidation of shared services is actually harmful, contradicting the article's warning framing
  • ~Modern permission systems and bureaucracy make cross-boundary work impossible in practice
19.The Google Play app review process now regularly takes longer than a week(gultsch.social)
361 points by inputmice 27 days ago | 348 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • ↑Confirms long Google Play review times with personal examples of multi-week waits
  • ↑Notes review times are wildly inconsistent, disrupting release cadence
  • ↑Apple's App Store review process is suffering from similar delays
  • ↑LLM-generated app explosion is creating a bottleneck in human review queues
  • ↓Personal experience contradicts the article—reviews remain fast and automated
20.Salesforce Global Outage(status.salesforce.com)
276 points by mabil 27 days ago | 183 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • ↓Salesforce's SRE team is competent and running a massive PaaS is genuinely challenging
  • ↑Mocking Salesforce's remediation attempts and restart-based troubleshooting
  • ↑Terrible timing given Dreamforce conference is happening this week
  • •Technical explanation of the root cause being a legacy login service resource exhaustion
  • ~The status page design is confusing and quintessentially Salesforce