frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Live: Artemis II Launch Day Updates

https://www.nasa.gov/blogs/missions/2026/04/01/live-artemis-ii-launch-day-updates/
712•apitman•10h ago•661 comments

A new C++ back end for ocamlc

https://github.com/ocaml/ocaml/pull/14701
119•glittershark•4h ago•7 comments

Quantum computing bombshells that are not April Fools

https://scottaaronson.blog/?p=9665
64•Strilanc•3h ago•5 comments

DRAM pricing is killing the hobbyist SBC market

https://www.jeffgeerling.com/blog/2026/dram-pricing-is-killing-the-hobbyist-sbc-market/
346•ingve•6h ago•279 comments

EmDash – A spiritual successor to WordPress that solves plugin security

https://blog.cloudflare.com/emdash-wordpress/
494•elithrar•11h ago•350 comments

Fast and Gorgeous Erosion Filter

https://blog.runevision.com/2026/03/fast-and-gorgeous-erosion-filter.html
95•runevision•1d ago•13 comments

Set the Line Before It's Crossed

https://nomagicpill.substack.com/p/set-the-line-before-its-crossed
41•surprisetalk•2d ago•18 comments

AI for American-produced cement and concrete

https://engineering.fb.com/2026/03/30/data-center-engineering/ai-for-american-produced-cement-and...
167•latchkey•10h ago•109 comments

Show HN: Git bayesect – Bayesian Git bisection for non-deterministic bugs

https://github.com/hauntsaninja/git_bayesect
221•hauntsaninja•4d ago•29 comments

Signing data structures the wrong way

https://blog.foks.pub/posts/domain-separation-in-idl/
82•malgorithms•7h ago•40 comments

The Claude Code Leak

https://build.ms/2026/4/1/the-claude-code-leak/
8•mergesort•1h ago•0 comments

Trinity Large Thinking

https://openrouter.ai/arcee-ai/trinity-large-thinking
15•kristianp•1h ago•6 comments

Ask HN: Who is hiring? (April 2026)

214•whoishiring•12h ago•176 comments

The revenge of the data scientist

https://hamel.dev/blog/posts/revenge/
111•hamelsmu•4d ago•21 comments

IPv6 address, as a sentence you can remember

https://sentence2ipv6.tib3rius.com/
41•LorenDB•4h ago•45 comments

Show HN: Dull – Instagram Without Reels, YouTube Without Shorts (iOS)

https://getdull.app
52•kasparnoor•6h ago•37 comments

Weather.com/Retro

https://weather.com/retro/
36•typeofhuman•1h ago•4 comments

The Windows equivalents of the most used Linux commands

http://techkettle.blogspot.com/2026/04/the-windows-equivalents-of-most-used.html
27•elsadek•5h ago•13 comments

InspectMind AI (YC W24) Is Hiring

https://www.ycombinator.com/companies/inspectmind-ai/jobs/jQNra64-software-engineer-build-the-wor...
1•aakashprasad91•6h ago

Solar Balconies Take Europe by Storm

https://hackaday.com/2026/03/31/solar-balconies-take-europe-by-storm/
22•lxm•1h ago•5 comments

SpaceX files to go public

https://www.nytimes.com/2026/04/01/technology/spacex-ipo-elon-musk.html
233•nutjob2•9h ago•300 comments

Ariane 6 user's manual [pdf]

https://www.ariane.group/app/uploads/sites/4/2024/10/Mua-6_Issue-2_Revision-0_March-2021.pdf
49•matthieu_bl•4d ago•6 comments

SolveSpace (open source 2D/3D CAD) working on Windows 2000 (2025)

https://github.com/solvespace/solvespace/issues/1036
23•ruevs•5h ago•3 comments

StepFun 3.5 Flash is #1 cost-effective model for OpenClaw tasks (300 battles)

https://app.uniclaw.ai/arena?tab=costEffectiveness&via=hn
149•skysniper•11h ago•64 comments

Scientists crack a 20-year nuclear mystery behind the creation of gold

https://www.sciencedaily.com/releases/2026/03/260313002633.htm
60•prabal97•8h ago•30 comments

BurgerDisk News

https://www.colino.net/wordpress/archives/2026/03/28/burgerdisk-news/
10•ibobev•2d ago•1 comments

Steam on Linux Use Skyrocketed Above 5% in March

https://www.phoronix.com/news/Steam-On-Linux-Tops-5p
8•hkmaxpro•27m ago•1 comments

Jax's true calling: Ray-Marching renderers on WebGL

https://benoit.paris/posts/jax-ray-marcher/
64•BenoitP•8h ago•8 comments

Show HN: Flight-Viz – 10K flights on a 3D globe in 3.5MB of Rust+WASM

https://flight-viz.com
66•coolwulf•10h ago•35 comments

Escaping the Ogallala Trap

https://worksinprogress.co/issue/escaping-the-ogallala-trap/
4•surprisetalk•2d ago•4 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.