frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Zig – io_uring and Grand Central Dispatch std.Io implementations landed

https://ziglang.org/devlog/2026/#2026-02-13
158•Retro_Dev•4h ago•81 comments

Show HN: I spent 3 years reverse-engineering a 40 yo stock market sim from 1986

https://www.wallstreetraider.com/story.html
386•benstopics•4d ago•139 comments

Show HN: SQL-tap – Real-time SQL traffic viewer for PostgreSQL and MySQL

https://github.com/mickamy/sql-tap
133•mickamy•8h ago•23 comments

The Three Year Myth

https://green.spacedino.net/the-three-year-myth/
86•surprisetalk•3d ago•46 comments

Understanding the Go Compiler: The Linker

https://internals-for-interns.com/posts/the-go-linker/
99•valyala•5d ago•18 comments

YouTube as Storage

https://github.com/PulseBeat02/yt-media-storage
62•saswatms•3h ago•53 comments

Babylon 5 is now free to watch on YouTube

https://cordcuttersnews.com/babylon-5-is-now-free-to-watch-on-youtube/
290•walterbell•1d ago•139 comments

Show HN: Data Engineering Book – An open source, community-driven guide

https://github.com/datascale-ai/data_engineering_book/blob/main/README_en.md
181•xx123122•15h ago•21 comments

Ars Technica makes up quotes from Matplotlib maintainer; pulls story

https://infosec.exchange/@mttaggart/116065340523529645
76•robin_reala•3h ago•19 comments

GPT-5.2 derives a new result in theoretical physics

https://openai.com/index/new-result-theoretical-physics/
507•davidbarker•17h ago•339 comments

How the Little Guy Moved

https://animationobsessive.substack.com/p/how-the-little-guy-moved
47•zdw•4d ago•1 comments

Common Lisp Screenshots: today's CL applications in action

http://www.lisp-screenshots.org
126•_emacsomancer_•2d ago•39 comments

NPMX – a fast, modern browser for the NPM registry

https://npmx.dev
112•slymax•10h ago•44 comments

Cogram (YC W22) – Hiring former technical founders

https://www.ycombinator.com/companies/cogram/jobs/LDTrViN-ex-technical-founder-product-engineer
1•ricwo•5h ago

The World of Harmonics – With a Coffee, Guitar and Synth

https://mynoise.net/vlog.php?ep=20260204
20•gregsadetsky•4d ago•4 comments

Building a TUI is easy now

https://hatchet.run/blog/tuis-are-easy-now
242•abelanger•18h ago•188 comments

Backblaze Drive Stats for 2025

https://www.backblaze.com/blog/backblaze-drive-stats-for-2025/
99•Brajeshwar•8h ago•16 comments

Font Rendering from First Principles

https://mccloskeybr.com/articles/font_rendering.html
167•krapp•6d ago•30 comments

The Sling: Humanity's Forgotten Power

https://www.slinging.org/
11•jsattler•4d ago•2 comments

The mathematics of compression in database systems

https://www.bitsxpages.com/p/the-mathematics-of-compression-in
7•agavra•3d ago•0 comments

Gradient.horse

https://gradient.horse
279•microflash•4d ago•56 comments

The EU moves to kill infinite scrolling

https://www.politico.eu/article/tiktok-meta-facebook-instagram-brussels-kill-infinite-scrolling/
640•danso•15h ago•666 comments

Monosketch

https://monosketch.io/
793•penguin_booze•1d ago•134 comments

Adventures in Neural Rendering

https://interplayoflight.wordpress.com/2026/02/10/adventures-in-neural-rendering/
33•ingve•3d ago•1 comments

Fix the iOS keyboard before the timer hits zero or I'm switching back to Android

https://ios-countdown.win/
1477•ozzyphantom•22h ago•727 comments

gRPC: From service definition to wire format

https://kreya.app/blog/grpc-deep-dive/
134•latonz•5d ago•21 comments

CSS-Doodle

https://css-doodle.com/
175•dsego•1d ago•17 comments

The wonder of modern drywall

https://www.worksinprogress.news/p/the-wonder-of-modern-drywall
119•jger15•1d ago•186 comments

WolfSSL sucks too, so now what?

https://blog.feld.me/posts/2026/02/wolfssl-sucks-too/
128•thomasjb•1d ago•101 comments

Advanced Aerial Robotics Made Simple

https://www.drehmflight.com
131•jacquesm•5d ago•11 comments
Open in hackernews

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

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

Comments

MacsHeadroom•9mo 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•8mo 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•9mo 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•9mo ago
do you have references to

> TTT, cannon layers, and titans

najarvg•9mo 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•9mo ago
is titans replicated? I feel like lucidrains couldn't replicate.
logicchains•9mo 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•9mo 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•9mo 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•9mo 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•9mo 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.