frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

How to Turn Anything into a Router

https://nbailey.ca/post/router/
180•yabones•2h ago•70 comments

Parrots pack twice as many neurons as primate brains of the same mass

https://www.dhanishsemar.com/writing/bird-brains
122•DiffTheEnder•2h ago•62 comments

Mathematical methods and human thought in the age of AI

https://arxiv.org/abs/2603.26524
114•zaikunzhang•4h ago•38 comments

72% of the dollar's purchasing power was destroyed in just four episodes

https://eco3min.fr/en/us-inflation-is-not-linear/
17•latentframe•52m ago•1 comments

The curious case of retro demo scene graphics

https://www.datagubbe.se/aipixels/
292•zdw•10h ago•71 comments

ChatGPT won't let you type until Cloudflare reads your React state

https://www.buchodi.com/chatgpt-wont-let-you-type-until-cloudflare-reads-your-react-state-i-decry...
847•alberto-m•19h ago•550 comments

I use excalidraw to manage my diagrams for my blog

https://blog.lysk.tech/excalidraw-frame-export/
185•mlysk•8h ago•83 comments

Build123d: A Python CAD programming library

https://github.com/gumyr/build123d
10•Ivoah•18h ago•1 comments

"Over 1.5 million GitHub PRs have had ads injected into them by Copilot"

https://www.neowin.net/news/microsoft-copilot-is-now-injecting-ads-into-pull-requests-on-github-g...
57•bundie•41m ago•23 comments

In Math, Rigor Is Vital. But Are Digitized Proofs Taking It Too Far?

https://www.quantamagazine.org/in-math-rigor-is-vital-but-are-digitized-proofs-taking-it-too-far-...
30•isaacfrond•4d ago•20 comments

Ghostmoon.app – The Swiss Army Knife for your macOS menu bar

https://www.mgrunwald.com/ghostmoon/
121•mgrunwald_•4h ago•90 comments

The coming PLG to SLG apocalypse

https://www.withsahel.com/blog/plg-to-enterprise-timeline-compression
13•iajiboye•4d ago•5 comments

Hamilton-Jacobi-Bellman Equation: Reinforcement Learning and Diffusion Models

https://dani2442.github.io/posts/continuous-rl/
103•sebzuddas•8h ago•28 comments

Spring Boot Done Right: Lessons from a 400-Module Codebase

https://medium.com/all-things-software/spring-boot-done-right-lessons-from-a-400-module-codebase-...
48•dknj•3d ago•35 comments

Comprehensive C++ Hashmap Benchmarks (2022)

https://martin.ankerl.com/2022/08/27/hashmap-bench-01/
35•klaussilveira•5d ago•11 comments

Voyager 1 runs on 69 KB of memory and an 8-track tape recorder

https://techfixated.com/a-1977-time-capsule-voyager-1-runs-on-69-kb-of-memory-and-an-8-track-tape...
622•speckx•23h ago•230 comments

Copilot edited an ad into my PR

https://notes.zachmanson.com/copilot-edited-an-ad-into-my-pr/
1115•pavo-etc•11h ago•321 comments

VHDL's Crown Jewel

https://www.sigasi.com/opinion/jan/vhdls-crown-jewel/
105•cokernel_hacker•11h ago•37 comments

15 Years of Forking

https://www.waterfox.com/blog/15-years-of-forking/
255•MrAlex94•2d ago•54 comments

How Reverse Game Theory Could Solve the Housing Shortage

https://www.noemamag.com/the-architecture-of-cooperation/
19•bookofjoe•5h ago•16 comments

Ninja is a small build system with a focus on speed

https://github.com/ninja-build/ninja
60•tosh•3d ago•17 comments

C++26 is done: ISO C++ standards meeting Trip Report

https://herbsutter.com/2026/03/29/c26-is-done-trip-report-march-2026-iso-c-standards-meeting-lond...
287•pjmlp•21h ago•297 comments

How the AI Bubble Bursts

https://martinvol.pe/blog/2026/03/30/how-the-ai-bubble-bursts/
284•martinvol•3h ago•337 comments

The First Video Game Was Just a Box in the Corner of a Bar

https://lithub.com/the-very-first-video-game-was-just-a-box-in-the-corner-of-a-bar/
28•PaulHoule•3d ago•25 comments

Douglas Lenat's Automated Mathematician Source Code

https://github.com/white-flame/am
51•hydrolox•4d ago•7 comments

Hardware Image Compression

https://www.ludicon.com/castano/blog/2026/03/hardware-image-compression/
50•luu•1d ago•9 comments

Philly courts will ban all smart eyeglasses starting next week

https://www.inquirer.com/news/philadelphia/smart-glasses-ai-meta-courts-20260326.html
351•Philadelphia•14h ago•173 comments

My MacBook keyboard is broken and it's insanely expensive to fix

https://tobiasberg.net/posts/my-macbook-keyboard-is-broken-and-its-insanely-expensive-to-fix/
305•TobiasBerg•20h ago•358 comments

Coding agents could make free software matter again

https://www.gjlondon.com/blog/ai-agents-could-make-free-software-matter-again/
245•rogueleaderr•17h ago•251 comments

Pretext: TypeScript library for multiline text measurement and layout

https://github.com/chenglou/pretext
350•emersonmacro•1d ago•62 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•10mo 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.