Hacker News

Top stories

Live mirror
30 storiesupdated just nowView source snapshot
  1. Astra for Law(openai.com ↗)
    361comments
  2. Bonsai 2 27B: Near-Lossless Compression in a 9x Smaller Footprint(prismml.com ↗)
    75comments
  3. Goose: 1.16x faster than C++ and 1.12x than safe Rust, while memory safe(github.com/aardappel ↗)
    24comments
  4. Bend – A language that blocks AI mistakes via proof, on CPU and GPU(bend-lang.com ↗)
    153comments
  5. Hister: A private search engine for the pages you visit and the files you keep(github.com/asciimoo ↗)
    137comments
  6. Wax motor(wikipedia.org ↗)
    50comments
  7. Fujitsu launches made-in-Japan next-generation CPU FUJITSU-MONAKA(global.fujitsu ↗)
    198comments
  8. Alibaba releases Qwen 3.8 Omni Flash(qwen.ai ↗)
    5comments
  9. Telstra outage: The night a network decided the year was 2006(netnod.se ↗)
    2comments
  10. Flet 1.0 – Build cross-platform apps in Python(flet.dev ↗)
    34comments
  11. Diplodocus, Long Thought Exclusively American, Turns Up in Spain(sci.news ↗)
    20comments
  12. More than 100k people in Japan are now aged 100 or older(bbc.com ↗)
    122comments
  13. I Put Nam A2-Lite Inside an iRig HD X(playtaurus.com ↗)
    1comments
  14. CrowdSec Source Code Leak(crowdsec.net ↗)
    40comments
  15. Infinite-Parameter LLMs: Generating and Adapting Weights from Live Data(arxiv.org ↗)
    34comments
  16. How Uber Protects Against Retry Storms(uber.com ↗)
    23comments
  17. Why I didn’t sign the Fields medallists’ letter(gowers.wordpress.com ↗)
    313comments
  18. The most important product decision is what you don't build(liamnugent.me ↗)
    19comments
  19. Rate limits on GitLab.com are changing(about.gitlab.com ↗)
    106comments
  20. How do we prevent mathemathics from devolving into the Medieval Era of secrecy?(mathoverflow.net ↗)
    56comments
  21. CCC invites all model citizens to 40C3(ccc.de ↗)
    180comments
  22. TSMC revealing details about next gen A14 node(mapyourshow.com ↗)
    36comments
  23. The American Religion of Self-Storage Facilities(newyorker.com ↗)
    343comments
  24. Landing the Space Shuttle – A Flying Machine and the Thrill of a Lifetime(eaa.org ↗)
    5comments
  25. Zettascale (YC S24) Is Hiring ASIC/FPGA Engineers to Build Chips for ASI(zscc.ai ↗)
    discuss
  26. Show HN: Snapdrop: Instantly share files between devices. No setup, no signup(snapdrop.me ↗)
    19comments
  27. Running Ubuntu on the Lenovo IdeaPad Duet(vhaudiquet.fr ↗)
    25comments
  28. Computer Reset, Dallas(dfarq.homeip.net ↗)
    2comments
  29. Launch HN: Skillsync (YC W26) – AI chat sessions made portable across agents
    50comments
  30. Show HN: Share your AI Setup, Learn from others(mysetup.ai ↗)
    103comments

Show HN: Lexplain – AI-powered Linux kernel change explanations

4 pointsby 5mo agolexplain.net
0 comments
To understand what changed between kernel versions, you have to dig through the git repository yourself. Commit messages rarely tell you the real-world impact on your systems — you need to analyze the actual diffs with knowledge of kernel internals. For engineers who use Linux — directly or indirectly — but aren't kernel developers, that barrier is pretty high.

I kept finding out about relevant changes only after an issue had already hit, and it was most frustrating when the version was too new to find similar cases online. I built lexplain with the idea that it would be nice to quickly scan through kernel changes the way you'd skim the morning news.

It reads diffs, analyzes the code, and generates two types of documents:

- Commit analyses: context, code breakdown, behavioral impact, risks, references

- Release notes: per-version highlights, functional classification, subsystem breakdown, impact analysis

Documents build on each other — individual commits first, then merge commits using child analyses, then release notes using all analyses for that version. Claims based on inference are explicitly labeled.

Work in progress. Feedback welcome.

A quiet thread, for now.Start the conversation on HN ↗