I really wish Rust crates had binary distributions. Compile times are still an order of magnitude too slow.

I don't get why I would bother with this lol gist.github.com/MostAwesomeD... Maybe someone who's in a more "influencer" space might. But "I am tired of hearing the fallacious claim that [...] those same chatbots are able to develop any software whatsoever." is obviously true to me so who cares?

I stopped paying attention to the rust subreddit for years. Looking at it lately, it's absolute dogshit. Is this just fallout from so many rust devs moving to other forums/ leaving the community? It's a bad look to have it suck so hard.

Quick quiz: how many people in S.F. were killed by Waymos this week? How many people in S.F. were killed by human drivers this week? (The answers are zero and two, but no one would know that from the reactions today.)

Github Actions was bad on release and hasn't really improved since then. Moving to depot is 30 seconds of work and will give you 10x performance, radically better UX, and 50% of the cost. I have no idea what bonehead thought that GHA should fuck with pricing right now.

Inability to trivially mock in Rust is a real problem. Similarly, inability to assert things like "a method was called N times" etc. This would be invaluable for formally verifying some aspects of my algorithms (ie: optimizations that ensure O(N) etc) via properties of tests.

I think the dependency "cooldown" approach is fundamentally flawed and a total distraction from the work that would actually solve supply chain issues - sandboxing and attestation. insanitybit.github.io/2025/11/22/o...

Doing a thing with wasm again. I always end up disappointed, let's see how it goes this time!

news.ycombinator.com/item?id=4556... Interesting how broken your epistemology has to be to say something like this. "We call it X therefor it is X".

Trying to modularize crates so that the entire API surface and implementation of each can fit into a small context window.

I totally get why people think this (due to how rapidly the SOTA has changed), but it's not really accurate. Transformer models operate in high-dimensional embedding spaces where semantic relationships differ from surface form. It's not just about the text. It's the meanings, the relationships.

Lobste.rs AI discussions are so cringe. I mostly don't visit the site at this point because it's basically just 1 or 2 commenters providing value, but when I do and I see AI convos they're just hard to read. lobste.rs/s/xbxhvq/vib... Simon does good work, idk why he tries to talk to these people.

An interesting thing about "a malicious package grabbed keys from the system" is that this problem has 0 technical or UX considerations and has been solved by browsers for over 20 years. Sandboxing is the solution. That is it. UX for sandboxing is solved, look at manifests and how changes surface.

Two things I feel comfortable "vibe coding" (ie: with loose guidance, allowing a model to drive). 1. After my own tests are written, asking for additional "Given/ When/ Then" tests to be written based on expected properties of the code. 2. Reduction of code to reduce LOC. "That could be a fn"

Feels nuts that Github Actions doesn't provide basic features like restricting outbound networking. This feels like it would be so dead simple for them to implement?

Claude is far too nice and not nearly as skeptical as I want it to be. I suppose second guessing and checking assumptions is very expensive but it's frustrating, and I've found that I need to have a second model in a sort of "skeptical mode" to compensate.

Safer drivers, stronger devices (with #rustlang) techcommunity.microsoft.com/blog/surface...

OpenAI's Codex needs a lot more work.

Very glad that "function coloring is good" has stopped being such a hot take.

I wonder how much ChatGPT usage spikes on Prime Day

Support for atoms is now implemented.

Running into a particularly challenging issue. I want anonymous structs in my language. Doing this in a way that's zero cost + compiling to Rust is *hard*. In particular, the first pass I have is to gen `HasX` traits for each prop, but then rust borrows the entire `self`, making moves impossible.

My language is now faster than rust... sometimes. Faster default hasher + the effects system opens up novel optimization opportunities.

got capabilities done

Spent time writing some basic optimizations for codegen. I've doubled the performance of some operations. Still much slower than Rust, but I'm about to write a CFG to do a lot more optimization. And there's still low hanging fruit.

My language now supports inference of union types in a way that's really neat and compiles to a rust enum under the hood. Full Hindley-Milner with unification, lots of type tracking info that I may use later like *where* a type comes from (for flow typing and refining later!).

Anyone aware of good type system stuff for GC'd languages that track mutable vs immutable references? Seems like you basically end up with regular reference types + specially marked "unique" types where unique types have tracked references.

Writing this programming language and documenting it all as I go. Then I give cursor a prompt to try learning the language from docs and generate test projects as it goes, validating every bit of documentation. Either it finds bugs in the docs or bugs in the compiler, extremely helpful.

Time to try to give my programming language reference types.

I'm building a lil programming language that compiles to Rust. It's GC'd, much friendlier type system, more limited in power, but lets you write inline Rust as-needed. Big feature is capabilities. Compiles and works, just need to improve the type inference (limited Hindley-Milner right now).

lore.kernel.org/all/20250531... Linus is such a moron.

I wasn't sure if I would really bother joining bsky but I pretty much instantly got value from just going to @scottpiper.bsky.social 's feed so maybe I'll stick around a bit!