This is awesome. Almost all of these are believable even if you're looking at pretty carefully. I need this on a firestick or something.

This is awesome. Got completely lost reading this and was struggling to figure out where I got this link from. Amazing story.

Yep, I recall one of the big components being libc i18n

There was this very interesting paper out of Stanford this last September about pretraining under the unlimited compute but limited data paradigm[0]. Pretty much exactly the same thing but with ~200M training tokens instead.

[0] https://www.alphaxiv.org/abs/2509.14786

yeah, we do incorporate some of the findings from the paper in our repo! like aggressive regularization and ensembling.

I see you already mention diffusion - iirc there was a result not too long ago that diffusion models keep improving with more epochs for longer than AR models do.

diffusion is promising, but still an open question how much data efficient they are compared to AR. in practice, you can also train AR forever with high enough regularization, so let's see.

Yes, it could go either way of course.

Still, just for reference, here's the paper I remembered: https://arxiv.org/pdf/2507.15857

thanks, here's another one: https://arxiv.org/abs/2511.03276

Not understanding the difference between this and something like cargo audit[0]. I suppose it has something to do with "static analysis of vulnerabilities" but I don't see any of that from a quick google search of govulncheck.

[0]https://crates.io/crates/cargo-audit

govulncheck analyzes symbol usage and only warns if your code reaches the affected symbol(s).

I’m not sure about cargo audit specifically, but most other security advisories are package scoped and will warn if your code transitively references the package, regardless of which symbols your code uses.

Oops. A better link would have been https://eieio.games/blog/secure-massively-multiplayer-snake/.

Thought this was AWS ECS – turns out it was much more interesting! I love entity component systems conceptually, glad to see data oriented design being discussed (even if it's not necessarily positive)

Would recommend that folks start with the original post for context: https://blog.ptidej.net/ecs-survivors-part-i/

I also thought this was going to be about folks who'd migrated off AWS ECS.

Here I was hoping for something about Amiga OCS, ECS, and AGA. ;)

Why? Sharding on lower bits seems fine to me.

Dupe of https://news.ycombinator.com/item?id=47055723

Oh! Poem guy is back, hey!

I like seeing this analysis on new model releases, any chance you can aggregate your opinions in one place (instead of the hackernews comment sections for these model releases)?