Hacker News

New stories

Live mirror
30 storiesupdated just nowView source snapshot
  1. Interview with Big Data engineer in 2026 [video](youtube.com ↗)
    discuss
  2. Blast Radius 1.0(dpdns.org ↗)
    discuss
  3. Show HN: BiNeuron – Local, open-source alternative to ChatGPT Codex(github.com/just-not-google ↗)
    discuss
  4. Everybody's Lost Their Minds(netmeister.org ↗)
    discuss
  5. Build your own Devin in one prompt(github.com/cayu-dev ↗)
    discuss
  6. Monsanto's Cruel, and Dangerous, Monopolization on American Farming (2008)(vanityfair.com ↗)
    discuss
  7. California may gut state net neutrality law to comply with Trump admin demand(arstechnica.com ↗)
    discuss
  8. Overlord – a trust kernel for AI agents(github.com/b1tr0n1n ↗)
    discuss
  9. PickiPedia: Artifical_Dumb(pickipedia.xyz ↗)
    discuss
  10. RL Is Everything, Everywhere, All at Once(skypilot.ai ↗)
    1comments
  11. Show HN: Pqp, an open-source Discord alternative with watch parties(github.com/rafaelcg ↗)
    discuss
  12. Ctenophores: Wonders of Biology(quantamagazine.org ↗)
    discuss
  13. Understanding Why You'd Use Effect TS(cm.xyz ↗)
    discuss
  14. Show HN: Spendalyst – tells you when a recurring charge changes price(spendalyst.com ↗)
    discuss
  15. CV Forge – tailor your resume to any job with AI(lumnika.com ↗)
    discuss
  16. Where Rust Ends and the Kernel Begins(acm.org ↗)
    discuss
  17. Mission Kit(missionkit.io ↗)
    1comments
  18. Evaluating S2S Model Quality with Human Preference Data(withdavid.ai ↗)
    discuss
  19. "Start with a Monolith" Was Good Advice. AI Is Changing That(medium.com/scalar-engineering ↗)
    1comments
  20. Snap launches $2,195 Specs smart glasses(yahoo.com ↗)
    discuss
  21. DeepSeek-v4.1 Flash: Pushing the Limits of KV Cache Compression(zartbot.github.io ↗)
    discuss
  22. What regulatory capture actually looks like(marginalrevolution.com ↗)
    1comments
  23. Tin: full-text search for Postgres(planetscale.com ↗)
    discuss
  24. Part-human part-mouse brain developed in science breakthrough(bbc.com ↗)
    discuss
  25. Show HN: FastRecall, ultra-cheap memory across AI models(fastrecall.ai ↗)
    discuss
  26. Michael Burry slams OpenAI, Anthropic for 'self-serving' calls to slow AI(nypost.com ↗)
    discuss
  27. Spanish data watchdog publicises first AI agent-linked data breach report(reuters.com ↗)
    discuss
  28. Xcode-Project-Format(github.com/apple ↗)
    discuss
  29. Flowchart: How pixels become an Apple Reference Image(claude.ai ↗)
    discuss
  30. Supply Chain Compromise of Korean-Language Windows 11 Installation Media(logpresso.com ↗)
    1comments

Migrating the GitHub Copilot Runtime to Rust, Using Copilot

4 pointsby 1h agogithub.blog
1 comments
1h agoHN ↗

In my personal experience, GitHub Copilot is pretty weak. Maybe it's just that I've used smaller models on it, but it just felt like the worst available harness, even behind Google Antigravity's.

Is there any redeeming quality to it nowadays? I'm curious what those eight hundred thousand lines of Rust actually do.

From what I understand, this runtime is used across a bunch of other Microsoft products with the "Copilot" naming. Does anyone understand Microsoft's current naming scheme regarding these products? I couldn't get even GPT 6 Astra to explain it reasonably to me.

Well, I guess I'm not even going to comment on my personal experience with Microsoft Copilot, or whatever bs that dashboard that launches the Office apps with an integrated AI chat is called.

Lastly, but not least:

   > During the port, the runtime took in ~300,000 production lines of TypeScript and shed ~430,000, while ~1,200,000 production Rust lines entered and ~365,000 left. In other words, the apparent stability of the TypeScript line in the above graph was actually hiding significant amounts of TypeScript churn.

This is the part I find really interesting. The resulting runtime is ~830k lines of production Rust. Even using their estimate that ~430k lines of production TypeScript passed through the port, that's still nearly twice as much production code.

They also say that agents wrote most of the Rust. Given how verbose LLM-generated code tends to be, I'd really like to see some analysis of why the implementation grew that much. How much of it is Rust and the new architecture, and how much is simply code the agents generated because generating more code is cheap?

The article points at the hidden TypeScript churn, but to me the much more interesting number is that ~1.2 million lines of Rust entered and ~365k were subsequently removed.