How old are you, for curiosities sake? I'm born early 90s, fondly remembering me and a friend shaming all the rest of our group by singing this song (dramatically as well) as a duet whenever we were in (already loud) public spaces.
I'm 50, i have two boys ages 16 and 14. My wife was more into music than I was growing up (i grew up in rural areas, she grew up in the city). One of my favorite stories she has is helping Modest Mouse unload their van when playing in Dallas at Club Dada (small local venue) back in the 90s. She also has so many cool rave, hiphop, and sxsw stories from that era since she went to HS in Arlington TX (class of '95), UT for college, and then lived in NYC for a while dating a musician. Austin in the mid/late 90s was a very special place to be a young person.
Back in 1999, the UK had its first total solar eclipse for several decades and VH1 played the music video (though, not this one ;-)) on loop for an hour while it was happening.
I'm glad this is still on the Internet. It's exactly the sort of thing that almost never is, when I try to find it again several years after seeing it the first time.
About two years ago I was experimenting with ChatGPT vibecoding a snake game in the browser in elm, because elm is my favorite language. It was rough going and I concluded at the time that LLM‘s might kill elm. Today I use elm in production and LLMs are vastly better at it, and if anything I think LLM‘s might increase elm adoption because it is the ideal language for an LLM right now. It’s a simpler language than most, it’s stable, it has an opinionated architecture built into the language which causes most code bases to be very similar to one another
On that note, because of AI I've been more into music, bought a midi keyboard, got real DAW software setup. I've also finally built more and more with Rust, and have been reading more Rust docs. LLMs should never be an excuse not to learn the things you're using it for, those are the bad engineers. An LLM affords me the time to research and learn what it gave me so I can maintain it. It's easier to prompt about the problem if you understand it.
I do though I havent been blogging as much, its a blessing and a curse to have a SSG based blog. I would love to have an SSG engine that I can use remotely from anywhere, currently using Publii.
> I think LLM‘s might increase elm adoption because it is the ideal language for an LLM right now
Yes but no? It really just depends on the amount of elm in the training data and rlhf. I agree that structured frameworks/languages have codebases more similar to one another and that would ease generation. But that alone won't work and usually dev adoption is a total discourse per se
That's not why Elm is an ideal language for LLMs: it's because, if it compiles, it's most likely working software. Agentic workflows have gotten significantly better over the last year, so LLMs using languages like Elm, Haskell, or even Rust have an amazing feedback loop where even lower quality models can keep trying until things compile.
can keep failing til you're tired of having the agent running in loops, as I said it doesn't matter, agent tools are more effective with models trained with a lot of elm examples
Yet Elm due to its simplicity does not need a lot of examples. Language itself is small and blessed way to architecture things consist of few patterns. Then things are composable. This is ideal for LLMs.
The price for that is verbosity. What in other languages are hidden behind async and complicated libraries in Elm has to be done explicitly resulting in boilerplate. But that is never a problem for LLMs.
Then Elm compiler has one of the best error messages. This helps agents a lot.
Then Time Machine debugger is another big help for agents as they have access to the full execution trace of the program. The trace is much smaller than would be necessary for other languages and typically fits into content window.
Maybe it's improved, but I was very disappointed to find agents constantly tripping over significant white space with Elm (Claude Code). Always struck me as strange since they are very proficient with python... and Elm has been one of the most stable modern languages (so stable that people complain about it never changing!). I think the last time I tried was a year ago though, so I assume it has improved.
Good to know. I built https://github.com/pairshaped/hypertea to get some of Elm's safety in typescript while being easy for LLMs to use (this is basically just hyperapp in TS, with added elm-like guardrails). Maybe I'll go back to Elm now that LLMs are handling it better.
I don't think anyone complained about the language changing, it was a lack of trust in the language due to the compiler not getting any updates. You can still improve the compiler without having to change the language.
Yes. But that is about to change, and the compiler is now getting the updates it needs.
Mostly the compiler was fine, we could do with some bug fixes in core packages - not many, but there are a small number of long time bugs that should really be sorted.
> I think the last time I tried was a year ago though, so I assume it has improved.
I noticed that coding agents seemed to get pretty good around 2025 Oct/Nov.
If it's improved? My experience with Nickel-lang (probably as not-in-training-data as Elm) is coding agents have improved with this compared to last time I tried.
I started working with Elm in production again about a year ago and have bounced back and forth between codex and Claude code and haven’t noticed whitespace problems, so I would conclude it’s better but of course your mileage may vary
I was already working with elm (have been since Signals) and I was very disappointed in what agents (CC) produced. In contrast, I was pleased with the Rust code they produced.
Longstanding issues that prevent usage? Not for me and the projects I’ve been apart of. No doubt there are plenty of reported issues, and no doubt they truly negatively impact some users, but I would still much rather choose the usability and stability of Elm 0.19.1-2 than anything in the typescript ecosystem today
When I worked on an Elm app in 2020, my users reported compatibility issues with various browser extensions (e.g. Grammarly, 1Password). I personally would prioritize making my apps usable for my users over making the DX usable for myself, so I stopped using Elm for future projects.
Well, you're suggesting a reason to choose Elm is stability - a lack of breaking changes. But Elm is actually notorious for its wildly unpopular, dramatic, community-fracturing breaking changes. Backwards compatibility is not a concern for them.
It's a little tricky though, because the comment you were replying to was talking about the lack of updates. And in that sense, Elm is now very stable - no breaking changes (or any changes at all!) in seven years and counting.
(Although, for all the complaints about the React ecosystem: you can still write class-style React components, even though they were effectively deprecated when hooks were introduced just over seven years ago.)
OTOH, we have this blog post suggesting development on Elm is kicking up again. Which means more breaking changes might be incoming.
I agree that the stability is quite nice. But there are plenty of areas where the language could use some improvement - for instance, the ergonomics around writing nested Single Page Apps is pretty cumbersome.
Tom Brown
Chief Compute Officer
Anthropic
548 Market Street
San Francisco, CA 94104
Dear Mr. Brown:
Since the issuance of my previous letters, dated June 12, 2026 and June 26, 2026, Anthropic has taken steps in close coordination with the U.S. government to address the risks associated with Claude Mythos 5 and Claude Fable 5. Among other things, Anthropic has agreed to proactively detect and address security risks associated with the models; to work diligently with the U.S. government on protocols and standards and releases for Mythos, Fable, and future
models; and to inform the U.S. government of any malicious activity. In light of these actions and commitments, as well as the Bureau of Industry and Security's evaluation of the diversion risks now presented by Claude Mythos 5 and Claude Fable 5, the controls in the June 12 letter are withdrawn. A license is no longer required for the export, reexport, or in-country transfer, including deemed export or deemed reexport, of the Mythos or
Fable models. Commerce reserves the right to reevaluate the decisions made in this letter and the necessity of reimposing a license requirement, should circumstances change or should Anthropic
fail to adhere to its commitments.
If you have any questions about this letter, please contact me or the Under Secretary of
Commerce for Industry and Security, Jeffrey Kessler, at (202) 255-1864.
In the few days I had access to Fable 5, I asked it to migrate our toolchain from nix+npm to docker+pnpm. It damn-near one-shotted it. I spent over a week stress testing it in every way and found very few things it missed. I was shocked.
To preempt a question, our team has no knowledge or experience with nix, it was setup before the current team was in place by people who did have knowledge and experience of nix. The current team knows docker much better.
How can one do this safely? If I create a new, non-sudo user, can I install the MDM profile only for that user? I don't understand how this all works obviously so maybe this is a very dumb question
Users reporting 403 Forbidden responses when downloading NuGet packagesPartial Service Disruption
Incident Status
Partial Service Disruption
Components
Website, API
Locations
Google Compute Engine
March 11, 2026 03:29 UTC
IDENTIFIED
Starting from approximately 08:00 UTC on 2026-03-10, multiple users were unable to download NuGet packages due to 403 Forbidden errors. We have identified the cause, and are going through the process of reverting the MR
> In total, Coruna takes advantage of 23 distinct vulnerabilities in iOS, a rare collection of hacking components that suggests it was created by a well-resourced, likely state-sponsored group of hackers.
People have been hacking iOS since before it was called iOS and they weren't necessarily "well-resourced, likely state-sponsored". See geohot
RIP Ms Tyler, you will be missed