frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Fabrice Bellard Releases MicroQuickJS

https://github.com/bellard/mquickjs/blob/main/README.md
638•Aissen•5h ago•251 comments

X-ray: a Python library for finding bad redactions in PDF documents

https://github.com/freelawproject/x-ray
58•rendx•1h ago•18 comments

Terrence Malick's Disciples

https://yalereview.org/article/bilge-ebiri-terrence-malick
59•prismatic•3h ago•12 comments

We replaced H.264 streaming with JPEG screenshots (and it worked better)

https://blog.helix.ml/p/we-mass-deployed-15-year-old-screen
260•quesobob•5h ago•165 comments

Perfect Software – Software for an Audience of One

https://outofdesk.netlify.app/blog/perfect-software
66•ggauravr•3d ago•20 comments

Lua 5.5

https://lua.org/versions.html#5.5
155•km•1d ago•39 comments

Texas App Store Age Verification Law Blocked by Federal Judge

https://www.macrumors.com/2025/12/23/texas-app-store-law-blocked/
9•danso•59m ago•0 comments

Microspeak: North Star – The Old New Thing (2015)

https://devblogs.microsoft.com/oldnewthing/20151103-00/?p=91861
9•rbanffy•39m ago•1 comments

Help My c64 caught on fire

https://c0de517e.com/026_c64fire.htm
50•ibobev•3h ago•12 comments

HTTP Caching, a Refresher

https://danburzo.ro/http-caching-refresher/
29•danburzo•3h ago•4 comments

Towards a secure peer-to-peer app platform for Clan

https://clan.lol/blog/towards-app-platform-vmtech/
66•throawayonthe•5h ago•14 comments

Adobe Photoshop 1.0 Source Code (1990)

https://computerhistory.org/blog/adobe-photoshop-source-code/
402•tosh•5d ago•120 comments

Un-Redactor

https://github.com/kvthweatt/unredactor
25•kvthweatt•3h ago•32 comments

Meta is using the Linux scheduler designed for Valve's Steam Deck on its servers

https://www.phoronix.com/news/Meta-SCX-LAVD-Steam-Deck-Server
470•yellow_lead•5h ago•249 comments

Instant database clones with PostgreSQL 18

https://boringsql.com/posts/instant-database-clones/
357•radimm•15h ago•146 comments

I didn't realize my LG TV was spying on me until I turned off this setting

https://www.pocket-lint.com/lg-tv-turn-off-live-plus/
42•fcpguru•1h ago•21 comments

Fifty problems with standard web APIs in 2025

https://zerotrickpony.com/articles/browser-bugs/
46•dhruv3006•5d ago•6 comments

Show HN: Claude Wrapped in the terminal, with a WASM raymarcher

https://spader.zone/wrapped/
3•dboon•1h ago•0 comments

Go-boot: bare metal Go UEFI boot manager

https://github.com/usbarmory/go-boot
52•nateb2022•5d ago•13 comments

Toad is a unified experience for AI in the terminal

https://willmcgugan.github.io/toad-released/
113•nikolatt•1d ago•28 comments

Executorch: On-device AI across mobile, embedded and edge for PyTorch

https://github.com/pytorch/executorch
103•klaussilveira•5d ago•15 comments

Astrophotography Target Planner: Discover Hidden Nebulas

https://astroimagery.com/techniques/imaging/astrophotography-target-planner/
47•kianN•4d ago•4 comments

Space Math Academy

https://space-math.academy
32•dynamicwebpaige•3d ago•10 comments

What makes you senior

https://terriblesoftware.org/2025/11/25/what-actually-makes-you-senior/
175•mooreds•4d ago•90 comments

Local AI is driving the biggest change in laptops in decades

https://spectrum.ieee.org/ai-models-locally
158•barqawiz•22h ago•156 comments

LAVD: Meta's New Default Scheduler [pdf]

https://lpc.events/event/19/contributions/2099/attachments/1875/4020/lpc-2025-lavd-meta.pdf
15•todsacerdoti•3h ago•1 comments

10 years bootstrapped: €6.5M revenue with a team of 13

https://www.datocms.com/blog/a-look-back-at-2025
260•steffoz•15h ago•93 comments

An initial analysis of the discovered Unix V4 tape

https://www.spinellis.gr/blog/20251223/?yc261223
75•DSpinellis•4h ago•4 comments

Fixed-Wing Runway Design

https://www.wbdg.org/building/aviation/fixed-wing-runway-design
12•DarkContinent•3h ago•9 comments

iOS 26.3 brings AirPods-like pairing to third-party devices in EU under DMA

https://www.macrumors.com/2025/12/22/ios-26-3-dma-airpods-pairing/
190•Tomte•16h ago•147 comments
Open in hackernews

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

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

Comments

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

> TTT, cannon layers, and titans

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