-
korrents.com
Frontier AI coding agents can now fix complex compiler bugs like LTO issues in about fifteen minutes.Their words
Strap a frontier AI into a good coding harness, show it what's broken, give it all the sources (source.tar), and ~15 minutes later I have a patch.
What's been going on in w64devkit the past yearnullprogram.com
Related posts
Mitchell Hashimoto GitHub
The subject this post names, from the same vocabulary the directory files beliefs under, and the words it uses that this site has seen least often elsewhere. Posts are matched on those words alone — nothing here is a summary of this one.
Top people
Showing Profile →
Hiding
Hiding
20 September
14 September
6 September
4 September
30 August
29 August
-
Their words
A nix based Omarchy would be amazing. Want to see this!
28 August
27 August
-
Their words
Maybe Nix is like Rust: Amazing if you don't have to look at the code! I'm open to the idea that Omarchy Cinque could switch packaging system if I never have to look at nixlang, there are no ergonomic regressions, and we have full repo sovereignty.
26 August
From one piece Why performant code matters (but gets widely ignored), with Casey Muratori 2 beliefs, in the piece's order there
-
Their words
If I look at the assembly language output from that compiler, I know exactly what the CPU is being asked to do. And it's not that hard to be able to learn to read assembly language so that you can see very quickly is the CPU being asked to do the things that I think it should be asked to do them.
-
Their words
But it's the cost of the compiler not being able to do any optimizations. That's the actual cost. And that cost can be severe.
22 August
9 August
12 July
6 June
3 June
-
Their words
But if you ever want to get better at anything, and sometimes that depth, that nuance is the thing that leads to an invention, right? If you know how a compiler works, if you know how memory management works, that might give you enough information to say, "Oh, I can make a new programming language."
20 May
From one piece Why Rust is different, with Alice Ryhl 2 beliefs, in the piece's order there
-
Their words
I think the same kind of principle applies with agents in that they can talk to the compiler. It will tell them what to fix. So I guess this could be a case. We we'll see. But Rust could be a pretty promising candidate for to use for agents because they can get more feedback and it's just hard it's harder to to ship certain type of bugs or maybe impossible to have certain type of bugs.
-
Their words
I think this is kind of leads to another way that Rust really helps with reliability, which is that if you're refactoring, I think Rust is really good at telling you all the places you need to update. I've done this sometimes where I would refactor something. I change the code. I change the return type or whatever it is, and then I just fix the compiler errors and until the compiler stops shouting. And then once I've done that, I've updated every place I need to update.
13 May
From one piece TypeScript, C# and Turbo Pascal with Anders Hejlsberg 4 beliefs, in the piece's order there
-
Their words
You can have the compiler write the state machine. If you introduce syntax that allows you to indicate where you want to yield. And that's what await is.
-
Their words
That was always the idea, and that that goes back even to the predecessor of Turbo Pascal, this idea that it's not just a compiler. It's an experience, right? I mean, you don't just compile your programs. You also edit them. You also run them. You also debug them. You also have a runtime library. It all has to like fit together.
-
Their words
And quite honestly, language design is 90% the same and 10% new for for pretty much every language. Every language you build still has to have a compiler. Compiler is still built in a pretty much the same way.
+ 1 more
-
Their words
And so everything is lazy and deferred and functional and reusable inside the compiler. And it's a very different way of writing compilers than than what the textbooks will traditionally teach you.
5 April
11 March
-
Their words
I had a lot of my own ego and identity wrapped up in my sort of compiler background. It's all It's interesting, right? But it's it's not useful in any meaningful sense anymore.
24 February
4 February
-
Their words
As high-level programming cedes way to the prose compiler, making your goals and specs well understood to the ambiguity loop and showing good judgment is going to matter more than ever.
8 June 2025
-
korrents.com
Graphics chips have far more room for future performance gains than CPUs, which are nearing physical limits.Their words
GPUs are not nearly as restricted in their future progress as CPUs which are far more constrained in how they can physically improve (compiler-driven ILP only goes so far).
7 April 2025
9 March 2025
-
Their words
I'm hopeful this framework will turn out to be a much more robust style for writing performance-sensitive code, especially over time and as compilers evolve.
1 March 2025
1 August 2024
-
Their words, before
I’m also still not sure how much I like nix – it’s very confusing! But it’s helped me compile some software that I was struggling to compile otherwise, and in general it seems to install things faster than homebrew.
Their words now
I’ve mostly switched back to Homebrew, nix was interesting but overall I think it’s not worth the complexity for me
18 July 2024
26 January 2024
8 December 2023
26 October 2023
14 April 2019
5 March 2012
-
Usesrcmnd.app
FlashDevelopTheir words
For coding: I mostly use FlashDevelop, with the Adobe Flex compiler.
17 May 2010
Nothing matches.
What is a korrent?
A korrent is a belief a person has stated in their own words: one sentence stating the claim, backed by a quote and a source, kept at korrents.com.
Under a name here, the quoted block is what they actually said. The korrent beneath it is the claim those words support, in korrents' wording — tap it to see the record, its source, and who else holds it.
Nobody here wrote their own korrents. They are compiled from public statements, and a person can change their mind, which is recorded too.
About the English under a post
Some people here publish in a language other than English. Where they do, this site shows a machine translation beneath the post, in this typeface — the site's own, not theirs.
The post itself is never changed, moved or hidden: what is set in the serif above is exactly what the person published, and it is what to quote them on. A translation can be wrong in ways that matter, especially about tone.
Only the post's own words are translated. A quoted post, a linked article and a belief on korrents.com are left in their original language.