frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

CUDA-L2: Surpassing cuBLAS Performance for Matrix Multiplication Through RL

https://github.com/deepreinforce-ai/CUDA-L2
14•dzign•40m ago•2 comments

Multivox: Volumetric Display

https://github.com/AncientJames/multivox
168•jk_tech•4h ago•21 comments

Plane crashed after 3D-printed part collapsed

https://www.bbc.com/news/articles/c1w932vqye0o
78•toss1•48m ago•56 comments

Transparent leadership beats servant leadership

https://entropicthoughts.com/transparent-leadership-beats-servant-leadership
313•ibobev•8h ago•150 comments

Why are 38 percent of Stanford students saying they're disabled?

https://reason.com/2025/12/04/why-are-38-percent-of-stanford-students-saying-theyre-disabled/
299•delichon•3h ago•464 comments

It’s time to free JavaScript (2024)

https://javascript.tm/letter
599•pavelai•12h ago•317 comments

Hammersmith Bridge – Where did 25,000 vehicles go?

https://nickmaini.substack.com/p/hammersmith-bridge
33•tobr•2h ago•22 comments

PyTogether: Collaborative lightweight real-time Python IDE for teachers/learners

https://github.com/SJRiz/pytogether
40•indigodaddy•4h ago•2 comments

How elites could shape mass preferences as AI reduces persuasion costs

https://arxiv.org/abs/2512.04047
421•50kIters•13h ago•440 comments

Django 6 Released

https://docs.djangoproject.com/en/6.0/releases/6.0/
33•wilhelmklopp•34m ago•8 comments

I ignore the spotlight as a staff engineer

https://lalitm.com/software-engineering-outside-the-spotlight/
363•todsacerdoti•10h ago•160 comments

Show HN: Onlyrecipe 2.0 – I added all features HN requested – 4 years later

https://onlyrecipeapp.com/?url=https://www.allrecipes.com/turkish-pasta-recipe-8754903
85•AwkwardPanda•6h ago•75 comments

Feynman vs. Computer

https://entropicthoughts.com/feynman-vs-computer
47•cgdl•5h ago•18 comments

The RAM shortage comes for us all

https://www.jeffgeerling.com/blog/2025/ram-shortage-comes-us-all
228•speckx•2h ago•254 comments

Converge (YC S23) is hiring a martech expert in NYC

https://www.runconverge.com/careers/technical-customer-success-manager
1•janhenr•4h ago

Autism should not be treated as a single condition

https://www.economist.com/science-and-technology/2025/12/03/why-autism-should-not-be-treated-as-a...
139•bookofjoe•5h ago•202 comments

Fighting the age-gated internet

https://www.wired.com/story/age-verification-is-sweeping-the-us-activists-are-fighting-back/
113•geox•8h ago•99 comments

Launch HN: Browser Buddy (YC W24) – A recommendation system for Internet writing

https://www.browserbuddy.com/
29•alien0006•4h ago•24 comments

Microsoft drops AI sales targets in half after salespeople miss their quotas

https://arstechnica.com/ai/2025/12/microsoft-slashes-ai-sales-growth-targets-as-customers-resist-...
294•OptionOfT•6h ago•221 comments

Functional Quadtrees

https://lbjgruppen.com/en/posts/functional-quadtree-clojure
101•lbj•8h ago•37 comments

Yawning abyss of the decimal labyrinth

https://oh4.co/site/numogrammaticism.html
11•austinallegro•1w ago•0 comments

Who Hooked Up a Laptop to a 1930s Dance Hall Machine?

https://www.chrisbako.com/posts/2025-12-04-speelkok-museam
18•ChrisbyMe•2h ago•4 comments

PGlite – Embeddable Postgres

https://pglite.dev/
456•dsego•10h ago•98 comments

CJEU has made it effectively impossible to run a user-generated platform legally

https://www.techdirt.com/2025/12/04/eus-top-court-just-made-it-literally-impossible-to-run-a-user...
51•alsetmusic•1h ago•14 comments

A Most Important Mustard

https://www.asimov.press/p/arabidopsis
8•surprisetalk•3d ago•0 comments

A lost Amazon world just reappeared in Bolivia

https://www.frontiersin.org/news/2025/11/06/landscapes-that-remember-indigenous-peoples-thrived-a...
84•ashishgupta2209•3d ago•17 comments

Uncloud - Tool for deploying containerised apps across servers without k8s

https://uncloud.run/
325•rgun•15h ago•135 comments

RAM is so expensive, Samsung won't even sell it to Samsung

https://www.pcworld.com/article/2998935/ram-is-so-expensive-samsung-wont-even-sell-it-to-samsung....
320•sethops1•8h ago•295 comments

Tunnl.gg

https://tunnl.gg
137•klipitkas•11h ago•84 comments

Show HN: Chess on a Donut/Torus and Deep-Dive

https://mchess.io/donut
18•mannymakes•5d ago•5 comments
Open in hackernews

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

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

Comments

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

> TTT, cannon layers, and titans

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