frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

DeepSeek Harness

https://www.deepseek.com/en/harness/
128•Kuyawa•3h ago•39 comments

Pi 1.0

https://earendil.com/posts/pi-1-0/
1053•sergiotapia•10h ago•330 comments

How Singapore's government-run dating service works

https://www.singapore-samizdat.com/p/how-singapores-government-run-dating-service-firstdate-works
82•danielfoster•4h ago•37 comments

Shimano Bicycle Museum Review

https://inrng.com/2026/10/shimano-bicycle-museum/
15•pietroppeter•1h ago•0 comments

Clef: Open-weight decision models, and new RL fine-tuning platform

https://blog.cloudflare.com/clef-decision-models/
480•jasondavies•14h ago•171 comments

SvelteKit 3

https://svelte.dev/blog/sveltekit-3-is-here
208•sampsn•10h ago•68 comments

Several vulnerabilities have been discovered in the Linux kernel

https://lwn.net/Articles/1097401/
224•luispa•7h ago•148 comments

Automatic Transmission – a data-privacy study of connected vehicles

https://automatictransmission.khoury.northeastern.edu/index.html
161•rafaelc•10h ago•153 comments

Pi Durable

https://earendil.com/posts/pi-durable/
317•paulsmith•11h ago•38 comments

Ask HN: Who is hiring? (October 2026)

177•whoishiring•15h ago•178 comments

Turbo Haskell

https://comonad.com/reader/2026/turbo-haskell/
59•pjmlp•16h ago•4 comments

StreetComplete on iOS is now in public beta

https://github.com/streetcomplete/StreetComplete/issues/5421
549•Snowly•19h ago•144 comments

Git 3.0's upcoming SHA-256 default will be a costly mistake

https://blog.gitbutler.com/git-3-sha-256
305•chmaynard•13h ago•300 comments

Using Opus 5.5 to discover a new eyewitness record of the dodo

https://resobscura.substack.com/p/using-opus-55-to-discover-a-new-eyewitness
114•benbreen•9h ago•28 comments

To grieve, or not to grieve?

https://xenaproject.wordpress.com/2026/10/01/to-grieve-or-not-to-grieve/
40•stabbles•20h ago•5 comments

CSS Bed: Classless CSS themes to use as starting points in web development

https://www.cssbed.com
94•sea-gold•9h ago•26 comments

RIP, vector database

https://turbopuffer.com/blog/rip-vector-database
302•razin•14h ago•82 comments

ArXiv's Updated Rate Limit Policy

https://blog.arxiv.org/2026/10/01/updated-rate-limit-policy/
102•50kIters•10h ago•39 comments

Building reliable (and fast) directory sync

https://www.firezone.dev/blog/building-reliable-directory-sync
3•jamilbk•1h ago•0 comments

Show HN: Janus – Go binary that runs GGUF models via Vulkan on AMD/Intel/Nvidia

https://github.com/Vibra-Ingenn/Janus
64•Maverick617•9h ago•9 comments

Frog and Toad and the Increasingly Capable Machines

https://www.frogandtoad.ai/
110•supermdguy•8h ago•22 comments

Vote on which of Hacker News' challenges for AI have been met

https://stoppels.ch/goalposts/
127•stabbles•12h ago•126 comments

Various Projects Find Hidden SDR Capabilities in ESP32 Microcontrollers

https://www.rtl-sdr.com/various-projects-independently-find-hidden-sdr-capabilities-in-esp32-micr...
201•nkw•15h ago•30 comments

Oxygen-deprived underwater zones may not be “dead zones” but clue to early life

https://agupubs.onlinelibrary.wiley.com/doi/10.1029/2026AV002570
92•gumby•11h ago•6 comments

Cloudflare K2: serverless event streams

https://blog.cloudflare.com/cloudflare-k2-streams/
226•elffjs•16h ago•89 comments

Butterflies use optical illusions to dodge predators

https://www.essex.ac.uk/news/2026/09/30/butterflies-use-optical-illusions-to-dodge-predators
35•gmays•7h ago•5 comments

Context Language Models

https://arxiv.org/abs/2609.37725
137•emersonmacro•15h ago•29 comments

Bez: Generating a browser engine from specs and tests

https://tangled.org/burrito.space/bez
108•nerdypepper•12h ago•44 comments

How to speed up the Rust compiler in September 2026

https://nnethercote.github.io/2026/09/30/how-to-speed-up-the-rust-compiler-in-september-2026.html
243•trickypr•17h ago•130 comments

US tells France and Germany to release diesel stocks or face US export ban

https://www.reuters.com/business/energy/us-tells-france-germany-release-diesel-stocks-or-face-us-...
12•geox•1h ago•4 comments
Open in hackernews

Attention Wasn't All We Needed

https://www.stephendiehl.com/posts/post_transformers/
130•mooreds•1y ago

Comments

andrewmcwatters•1y ago
I know this probably seems like such a small detail to a lot of people, but I really love that the author adds comments.

I can't stand reading PyTorch or other neural network code and asking myself, "What architecture am I looking at here?" or "What the hell are these operations for?"

It's always like an mash up of reading some published paper code with deep effort behind it along with all the worst programming practices of complete unreadability.

imranq•1y ago
Could you pop your code into an LLM and ask it to write comments for you? I'm not sure how accurate it is though
andrewmcwatters•1y ago
I've noticed leading models fail to understand what's happening in undocumented neural network code as well, so not yet it seems.
CamperBob2•1y ago
It may be a reasonable approach if you give the model a lot of clues to start with. Basically tell it everything you do know about the code.

I wouldn't expect miracles from just uploading a big .py file and asking it to add comments.

flebron•1y ago
This is an excellent summary of these techniques :) I like that every single one comes with an example implementation, with shape comments on the tensors. Thanks Stephen!
kouteiheika•1y ago
> Let's look at some of the most important ones that have been developed over the years and try to implement the basic ideas as succinctly as possible.

One big architectural tweak that comes to mind and isn't in the article is QK norm: https://arxiv.org/pdf/2010.04245

> Cosine Schedule

A lot (most?) of new training runs actually don't use cosine schedule anymore; instead they keep the learning rate constant and only decay it at the very end, which gives equivalent or better results. See:

https://arxiv.org/pdf/2405.18392 https://arxiv.org/pdf/2404.06395

> There is a highly optimized implementation of AdamW in PyTorch.

A fun tidbit - it's actually not highly optimized from my experience. Imagine my surprise when I reimplemented it in Triton (because I needed to tweak a few things) and I got better performance than the built-in PyTorch implementation.

Scene_Cast2•1y ago
RE: optimizer performance - any thoughts on heavyball?
kouteiheika•1y ago
...oh, I didn't know about this library, thanks!

I still probably wouldn't be able to use it because I need a bunch of custom functionality for my optimizers (like for example custom quantization support and incremental gradient accumulation directly in optimizers' state), but I might borrow some of their techniques if they make things even faster.

yorwba•1y ago
The explanation for Multi-head Latent Attention https://www.stephendiehl.com/posts/post_transformers/#multi-... does not match the definition in the DeepSeek-V2 paper https://arxiv.org/pdf/2405.04434#subsection.2.1

MLA as developed by DeepSeek is a technique to reduce the memory footprint of the KV cache by storing only two vectors of size latent_dim and rope_dim per token and layer, instead of 2 * num_heads vectors of size head_dim. (DeepSeek-V3 has num_heads = 128 and head_dim = 128 vs latent_dim = 512 and rope_dim = 64, so a significant reduction https://arxiv.org/pdf/2412.19437#subsection.4.2 )

What this article describes instead is some kind of two-step attention scheme I haven't seen before and that I think wouldn't work with causal masking (despite mask appearing in the example code) because either you allow an earlier token to attend to a latent that attended to a later token (creating backwards information flow) or the latents can only attend to a limited prefix of the sequence, after which they're frozen and useless. I wonder whether the author dreamed it up himself or whether someone else is actually using this somewhere.

jdeaton•1y ago
First four things on the list are attention
alanbernstein•1y ago
The title is a cute shortening of "Attention Is All You Need wasn't all we needed"
empiko•1y ago
Nice writeup, but regarding title -- I find it fascinating how powerful attention really is. There were some tweaks developedz sure, but if I open Llama 4 code on HugginFace, it is more or less the same code that I've seen there 5 years ago. Despite all the AI hype, we are still just exploiting tech developed in 2015-2020. And despite NeurIPS brandishing 25k papers this year, the innovation rate in deep learning seems to stagnate
kjkjadksj•1y ago
Too many horseriders, not enough horse breeders.
teleforce•1y ago
Nice analogy, most probably going to borrow it.
kouteiheika•1y ago
> There were some tweaks developedz sure, but if I open Llama 4 code on HugginFace, it is more or less the same code that I've seen there 5 years ago.

This is very much true. It's essentially the very same architecture, just tweaked slightly.

I can take the code I've written which implements the original GPT-2, tweak it very minimally (I don't know, maybe 30~40 lines of code changed?) and get Qwen3 which is a state-of-art model released ~3 weeks ago.

Contrary to what you might see when looking at e.g. HuggingFace code where every new architecture needs a new multi-thousand line of code file - that's just a result of an insane amount of copy-pasting and technical debt (although they started to clean it up a little bit lately). I have my own custom implementation which can load weights for ~19 different architectures straight off HuggingFace in like ~2k lines of code. They aren't really all that different.

danpalmer•
johnsmith1840•1y ago
One interesting thought process i've had around these topics is how it's not just attention but all DL methods suffer similar problems.

I truly believe the last step to AGI is solving continual learning. Efficient will always inch up but the "jump" is honestly not in sight.

Maybe attention + (unknown thing) really is all we need.

The thought is interesting because if you extrapolate that all DL models suffer the same class of problems (CL) the solution is implying two possibilities.

1. In the future, AGI level models will be entire new categories sharing little to nothing with methods like attention. (Every part is different like the article suggests)

2. Or (maybe more likely) we will simply build on what we have. If that's true then next generation models in agi like realm will be the same models we have now with one unifying change to all of them.

I previously made a unique transformer model whose every single neuron acted like a decision gate. Every neuron would choose a "computation nueron" before going on. Back prop was modified so that only computation neurons contributed to back prop of the next layer.

It had some interesting properties, the largest being that every token loop through the model was essentially seeing a completely different model. I was/am under the belief that scaling dimensionality == solving CL.

I bring it up because technically this architecture was identical to the transformer. I could drop my special neuron into literally any DL model out there and train.

I believe this kind of advancement is what will be the next generations models. Not a change of the transformer or attention but to the fundamental building blocks of all DL models.

It honestly does feel like attention gets us part of thr AGI equation well enough. It seems to have solved or will soon solve most short term hard problems. Again this is why CL is key, it's the timr comonent no AI method across the board has ever solved.

rusuereboutdat•1y ago
For the same reason Yann LeCun and everyone else says language won’t lead to AGI, nothing will lead to AGI.

Yann says language models need to be updated with new language to describe new observation.

But that’s not just with language. That’s physics. We cannot solve going to Mars or anything without the process.

But space time is endless and eventually some composition of it will come along the continuous learning machine has no ability to adapt to before it’s destroyed.

We’ve lost the information of the past and merely store simulation. We cannot see all of the future, just reduce to simulation.

Eventually any autonomous thing hits a snag it cannot solve before its destruction because in any reference frame it cannot know all the next best steps and know which past options to eliminate to simplify.

Energy based models will streamline away nonessential state to generating media and making a robot lift a box, like Linux and software like we know, but without 100% accurate data of the past and future (generation of which is impossible) whatever autonomous thing will eventually encounter a problem it never had time to solve and be smashed by the immutable churn of physics.

1y ago
The Llama models are substantially behind the state of the art, particularly when it comes to efficiency, they’re probably not the best example for adoption of these sorts of techniques.
BriggyDwiggs42•1y ago
I just… why can’t it adapt over time?
johnsmith1840•1y ago
Nobody knows.

It's one of those seemingly simple problems to which the solutions imply contradicting answers.

BriggyDwiggs42•1y ago
I just don’t get why we’re talking about cosmic scales but modern AI tech and not a hypothetical ASI a thousand years out with an iq of 2 million that would actually encounter these limits.
johnsmith1840•1y ago
Yeah that's not what I was talking about I was only talking about continual learning.

Just hijacked thr comment because my focus is on CL on current systems not the hypothetical.

BriggyDwiggs42•1y ago
Gotcha sorry. Got the wrong impression.
achierius•1y ago
Everything you're saying applies to humans too, though. We evolved, learned over time, and are now "AGI".