frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Don't post generated/AI-edited comments. HN is for conversation between humans.

https://news.ycombinator.com/newsguidelines.html#generated
1899•usefulposter•2h ago•742 comments

Temporal: A nine-year journey to fix time in JavaScript

https://bloomberg.github.io/js-blog/post/temporal/
415•robpalmer•6h ago•142 comments

Many SWE-bench-Passing PRs would not be merged

https://metr.org/notes/2026-03-10-many-swe-bench-passing-prs-would-not-be-merged-into-main/
32•mustaphah•1h ago•1 comments

Making WebAssembly a first-class language on the Web

https://hacks.mozilla.org/2026/02/making-webassembly-a-first-class-language-on-the-web/
323•mikece•17h ago•124 comments

Google closes deal to acquire Wiz

https://www.wiz.io/blog/google-closes-deal-to-acquire-wiz
182•aldarisbm•7h ago•125 comments

Show HN: I built a tool that watches webpages and exposes changes as RSS

https://sitespy.app
118•vkuprin•6h ago•35 comments

Personal Computer by Perplexity

https://www.perplexity.ai/personal-computer-waitlist
51•josephwegner•4h ago•35 comments

The MacBook Neo

https://daringfireball.net/2026/03/the_macbook_neo
307•etothet•10h ago•520 comments

Meticulous (YC S21) is hiring to redefine software dev

https://jobs.ashbyhq.com/meticulous/3197ae3d-bb26-4750-9ed7-b830f640515e
1•Gabriel_h•1h ago

Britain is ejecting hereditary nobles from Parliament after 700 years

https://apnews.com/article/uk-house-of-lords-hereditary-peers-expelled-535df8781dd01e8970acda1dca...
51•divbzero•1h ago•22 comments

BitNet: 100B Param 1-Bit model for local CPUs

https://github.com/microsoft/BitNet
276•redm•10h ago•141 comments

Entities enabling scientific fraud at scale (2025)

https://doi.org/10.1073/pnas.2420092122
242•peyton•8h ago•171 comments

Show HN: Klaus – OpenClaw on a VM, batteries included

https://klausai.com/
99•robthompson2018•6h ago•58 comments

I'm glad the Anthropic fight is happening now

https://www.dwarkesh.com/p/dow-anthropic
96•emschwartz•2h ago•94 comments

5,200 holes carved into a Peruvian mountain left by an ancient economy

https://newatlas.com/environment/5-200-holes-peruvian-mountain/
71•defrost•1d ago•41 comments

I was interviewed by an AI bot for a job

https://www.theverge.com/featured-video/892850/i-was-interviewed-by-an-ai-bot-for-a-job
61•speckx•4h ago•58 comments

Physicist Astrid Eichhorn is a leader in the field of asymptotic safety

https://www.quantamagazine.org/where-some-see-strings-she-sees-a-space-time-made-of-fractals-2026...
98•tzury•6h ago•14 comments

Can the Dictionary Keep Up?

https://www.thenation.com/article/culture/stefan-fatsis-dictionary-history/
5•pepys•1d ago•0 comments

How we hacked McKinsey's AI platform

https://codewall.ai/blog/how-we-hacked-mckinseys-ai-platform
355•mycroft_4221•12h ago•145 comments

Launch HN: Prism (YC X25) – Workspace and API to generate and edit videos

https://www.prismvideos.com
30•aliu327•6h ago•15 comments

Show HN: Satellite imagery object detection using text prompts

https://www.useful-ai-tools.com/tools/satellite-analysis-demo/
31•eyasu6464•2d ago•12 comments

Show HN: Open-source browser for AI agents

https://github.com/theredsix/agent-browser-protocol
85•theredsix•7h ago•26 comments

What Is a Tort?

https://harvardlawreview.org/print/vol-139/what-is-a-tort/
19•bookofjoe•2h ago•21 comments

Swiss e-voting pilot can't count 2,048 ballots after decryption failure

https://www.theregister.com/2026/03/11/swiss_evote_usb_snafu/
123•jjgreen•9h ago•291 comments

Launch HN: Sentrial (YC W26) – Catch AI agent failures before your users do

https://www.sentrial.com/
22•anayrshukla•6h ago•8 comments

Show HN: Vanilla JavaScript refinery simulator built to explain job to my kids

https://fuelingcuriosity.com/game.html
75•fuelingcurious•5h ago•37 comments

The dead Internet is not a theory anymore

https://www.adriankrebs.ch/blog/dead-internet/
280•hubraumhugo•2h ago•182 comments

Fungal Electronics (2021)

https://arxiv.org/abs/2111.11231
50•byt3h3ad•5h ago•6 comments

Building a TB-303 from Scratch

https://loopmaster.xyz/tutorials/tb303-from-scratch
200•stagas•4d ago•82 comments

Lego's 0.002mm specification and its implications for manufacturing (2025)

https://www.thewave.engineer/articles.html/productivity/legos-0002mm-specification-and-its-implic...
326•scrlk•9h ago•283 comments
Open in hackernews

EM-LLM: Human-Inspired Episodic Memory for Infinite Context LLMs

https://github.com/em-llm/EM-LLM-model
113•jbotz•10mo ago

Comments

MacsHeadroom•10mo ago
So, infinite context length by making it compute bound instead of memory bound. Curious how much longer this takes to run and when it makes sense to use vs RAG.
zfountas•9mo ago
Hi MacsHeadroom, first author here. Thanks for the great questions about compute/memory trade-offs.

The quick take: To give you an example of processing speed, with a 7B model on an NVIDIA V100, EM-LLM processes (or generates) about 326 tokens/sec with a 51.2K context window (which is quite competitive for these old GPUs).

More broadly, EM-LLM is designed to make ultra-long contexts (memory-prohibitive for standard O(n^2) attention) computationally tractable. The Appendix C of our paper https://openreview.net/pdf?id=BI2int5SAC details how: significantly better attention scaling, efficient O(nm) memory formation, and large KV cache management via CPU/disk offloading. While there's a slight per-chunk overhead compared to the simplest retrieval methods initially, the crucial part is our ability to handle sequences at scales infeasible for full-context models. For instance, we're successfully using 8B models with 10M token contexts on a single GPU without prohibitive delays.

Regarding RAG in particular, EM-LLM often shows significant gains on tasks needing deep understanding of a single, long, coherent context. A key reason is that EM-LLM allows each layer to retrieve and integrate relevant information from different "episodes" of the context independently, offering more nuance than a typical single RAG step, for similar overall resource use.

mountainriver•10mo ago
TTT, cannon layers, and titans seem like a stronger approach IMO.

Information needs to be compressed into latent space or it becomes computationally intractable

searchguy•10mo ago
do you have references to

> TTT, cannon layers, and titans

najarvg•10mo ago
This was the nearest reference I could find. Links to an unofficial pytorch implementation on Github are also linked in the threads somewhere - https://www.reddit.com/r/LocalLLaMA/comments/1i0q8nw/titans_...
vessenes•10mo ago
is titans replicated? I feel like lucidrains couldn't replicate.
logicchains•10mo ago
I think something like Titans explains Gemini's excellent long context performance. That would explain why the Titan team hasn't released the training code or hyperpameters used even though they said in the paper that they would, and why soon after that it came out that DeepMind would be holding off publishing new results for 6 months to avoid giving away competitive advantages.
p_v_doom•10mo ago
Interesting. Before there even was attention I was thinking that the episodic memory model offers something that could be very useful for neural nets, so its cool to see people testing that
killerstorm•10mo ago
Note that this works within a single sequence of tokens. It might be consistent with "episodic memory" metaphor if we consider a particular transformer run as its experience.

But this might be very different from what people expect from "memory" - i.e. ability to learn vast amounts of information and retrieve it as necessary.

This is more like a refinement of transformer attention: instead of running attention over all tokens (which is very expensive as it's quadratic), it selects a subset of token spans and runs fine-grained attention only on those. So it essentially breaks transformer attention into two parts - coarse-grained (k-NN over token spans) and fine-grained (normal).

It might be a great thing for long-context situations. But it doesn't make sense when you want millions of different facts to be considered - making them into long context is rather inefficient.

yorwba•10mo ago
It would be inefficient if you had to do it from scratch for every query, but if you can do it once as a preprocessing step and reuse the prepared context for many queries, it might start to become more efficient than a shorter context that includes only some documents but has to be reprocessed because it's different every time.
killerstorm•10mo ago
Yes, I think it might be a good solution where you have a context up to 10M of tokens and you do a lot of requests with that context. It might be relevant for agentic stuff which tends to produce long chat logs - especially with some gadgets on top, e.g. some 'episodes' might be completely removed as obsolete.

But I don't think it's a good solution for bigger amounts of data - as in that case it's more beneficial if that can be formed into independent memories.