Rust 1.100
Commenters highlight features in Rust 1.100: never type stabilization, custom allocators, dependency cooldowns, and unused dependency warnings.
30 stories
Get a notification every evening
You hear about the digest when it is ready. Turn it off any time.
Notifications are on
You will hear about each evening’s digest when it is ready.
To get notifications on iPhone or iPad, add this site to your Home Screen first: tap Share, then Add to Home Screen. Open it from there to turn notifications on.
Notifications are blocked in this browser. Allow them in site settings and reload.
New notification sign-ups are closed for now. You can follow along with RSS.
Notifications could not be turned on. Check your connection and try again.
Notifications could not be turned off and are still on. Check your connection and try again.
The day’s top discussions
Commenters highlight features in Rust 1.100: never type stabilization, custom allocators, dependency cooldowns, and unused dependency warnings.
Discussion revolves around whether the bug is true RCE or privilege escalation, and prepared statements not updating after table changes.
One commenter praises efforts to free devices from the cloud, while another argues central HVAC systems are better.
Commenters remember Tim Peters for his contributions to The Zen of Python and the SpamBayes project.
Discussion covers using Apple's Foundation Models without cloud API cost and using them in terminal for error correction.
One commenter builds a paper airplane from the site and is impressed, while another shares memories of a paper airplane book received in 1978.
Discussion compares AgentRun with Greptile and Sourcery, and questions how it differs from a simple harness.
The discussion revolves around how the perceived severity of major outages drops when everyone is affected.
One commenter compares the constant stream of security patches to cleaning an apartment only to have dust return days later.
One commenter reports that Relax failed on most of their Rust projects, miscompiled one, and found hot patching unusable.
One commenter notes the author is an OpenAI 'China hawk' influencer, not an academic, and urges verification of the claims.
One commenter notes that Java properties files can only be invalid if they contain invalid Unicode escape sequences.
One commenter says the video answers its own title, noting that organizations haven't changed what they optimize for.
Commenters note x402 hasn't seen transactions yet and only testers deposit money; one commenter praises the vision behind HTTP 402.
Commenters suggest adding llama.cpp and strata to the benchmark; also note Qwen3.8-flash.next runs well on a 4090 instead of Qwen3.6-35b-a3b.
Discussion focuses on differences like generating an MCP server instead of a CLI and using OpenAI API keys; one commenter notes token waste on failed browser actions.
Commenters suggest alternative approaches like speculative regeneration and small LLMs to detect end-of-speech earlier.
A commenter suggests de-AI-ifying the README and clearly explaining the `check` command's behavior.
A commenter notes that state space models feel like a homage to control of linear dynamical systems.
A commenter explains that SDFs are mathematical representations of implicit surfaces enabling realistic rendering via ray tracing.
A smaller, more technical community
One commenter praises showing how easy it can be to take control of your own computer, as an antidote to the 'taught helplessness' modern tech instills.
One commenter says the original article argued 'if the company is broken and you can't fix it, don't pay the price,' and this article explains that.
The week’s most-starred new repositories