frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Ghostty – Terminal Emulator

https://ghostty.org/docs
252•oli5679•5h ago•118 comments

Microgpt

http://karpathy.github.io/2026/02/12/microgpt/
1361•tambourine_man•16h ago•248 comments

AI Made Writing Code Easier. It Made Being an Engineer Harder

https://www.ivanturkovic.com/2026/02/25/ai-made-writing-code-easier-engineering-harder/
305•saikatsg•3h ago•214 comments

Long Range E-Bike

https://jacquesmattheij.com/long-range-ebike/
38•birdculture•3d ago•33 comments

Why XML Tags Are So Fundamental to Claude

https://glthr.com/XML-fundamental-to-Claude
51•glth•2h ago•18 comments

Decision trees – the unreasonable power of nested decision rules

https://mlu-explain.github.io/decision-tree/
260•mschnell•8h ago•45 comments

I built a demo of what AI chat will look like when it's "free" and ad-supported

https://99helpers.com/tools/ad-supported-chat
263•nickk81•5h ago•180 comments

Ape Coding

https://rsaksida.com/blog/ape-coding/
112•rmsaksida•3h ago•54 comments

We do not think Anthropic should be designated as a supply chain risk

https://twitter.com/OpenAI/status/2027846016423321831
692•golfer•20h ago•375 comments

Interview with Øyvind Kolås, GIMP developer (2017)

https://www.gimp.org/news/2026/02/22/%C3%B8yvind-kol%C3%A5s-interview-ww2017/
64•ibobev•3d ago•24 comments

Flightradar24 for Ships

https://atlas.flexport.com/
72•chromy•6h ago•24 comments

10-202: Introduction to Modern AI (CMU)

https://modernaicourse.org
153•vismit2000•10h ago•37 comments

MCP is dead. Long live the CLI

https://ejholmes.github.io/2026/02/28/mcp-is-dead-long-live-the-cli.html
5•ejholmes•50m ago•0 comments

New iron nanomaterial wipes out cancer cells without harming healthy tissue

https://www.sciencedaily.com/releases/2026/02/260228093456.htm
65•gradus_ad•2h ago•9 comments

Aromatic 5-silicon rings synthesized at last

https://cen.acs.org/materials/inorganic-chemistry/Aromatic-5-silicon-rings-synthesized/104/web/20...
47•keepamovin•2d ago•22 comments

Lil' Fun Langs' Guts

https://taylor.town/scrapscript-001
8•surprisetalk•2h ago•1 comments

The real cost of random I/O

https://vondra.me/posts/the-real-cost-of-random-io/
58•jpineman•3d ago•5 comments

Switch to Claude without starting over

https://claude.com/import-memory
413•doener•10h ago•204 comments

Why is the first C++ (m)allocation always 72 KB?

https://joelsiks.com/posts/cpp-emergency-pool-72kb-allocation/
92•joelsiks•8h ago•17 comments

An ode to houseplant programming (2025)

https://hannahilea.com/blog/houseplant-programming/
98•evakhoury•2d ago•17 comments

Obsidian Sync now has a headless client

https://help.obsidian.md/sync/headless
537•adilmoujahid•1d ago•176 comments

Robust and efficient quantum-safe HTTPS

https://security.googleblog.com/2026/02/cultivating-robust-and-efficient.html
72•tptacek•1d ago•10 comments

Show HN: Vertex.js – A 1kloc SPA Framework

https://lukeb42.github.io/vertex-manual.html
19•LukeB42•6h ago•13 comments

The happiest I've ever been

https://ben-mini.com/2026/the-happiest-ive-ever-been
590•bewal416•3d ago•317 comments

Rydberg atoms detect clear signals from a handheld radio

https://phys.org/news/2026-02-rydberg-atoms-handheld-radio.html
54•Brajeshwar•2d ago•20 comments

I Built a Scheme Compiler with AI in 4 Days

https://matthewphillips.info/programming/posts/i-built-a-scheme-compiler-with-ai/
7•MatthewPhillips•47m ago•1 comments

MCP server that reduces Claude Code context consumption by 98%

https://mksg.lu/blog/context-mode
510•mksglu•1d ago•95 comments

Pigeons and Planes Has a Website Again

https://www.pigeonsandplanes.com/read/pigeons-and-planes-has-a-website-again
30•herbertl•3d ago•3 comments

Hardwood: A New Parser for Apache Parquet

https://www.morling.dev/blog/hardwood-new-parser-for-apache-parquet/
83•rmoff•3d ago•9 comments

H-Bomb: A Frank Lloyd Wright typographic mystery

https://www.inconspicuous.info/p/h-bomb-a-frank-lloyd-wright-typographic
122•mrngm•3d ago•34 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•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•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.