korrents

compilers

Programs that turn programs into programs: what a compiler can name, assembly, and building one that serves an editor.

What people on korrents have said about compilers, newest first — 13 positions from 7 people.

FilterEveryone, all time
Who Everyone AHAnders Hejlsberg 4 CMCasey Muratori 3 ARAlice Ryhl 2 DRDax Raad 1 KHKelsey Hightower 1 SYSteve Yegge 1 THThePrimeagen 1
When All time Past 1 yearPast 3 yearsPast 5 years
  1. CM

    Casey Muratori quoted

    Our readingSource code in any language tells you nothing about what the CPU is actually asked to do; only the compiler's assembly output does, and reading it is a skill every serious programmer should have.

    Their wordsIf 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.

    ↗Why performant code matters (but gets widely ignored), with Casey Muratoriyoutube.com 6th of 26 in this recording

    Interesting
  3. CM

    Casey Muratori quoted

    Our readingAssembly is far simpler to learn than the modern web stack: anyone who can vertically centre a div can learn to read it.

    Their wordsit's really much easier if you can understand how to center a div as they say if you can vertically center a div in HTML then you can probably learn assembly language I would say

    ↗Why performant code matters (but gets widely ignored), with Casey Muratoriyoutube.com 7th of 26 in this recording

    Interesting
  5. CM

    Casey Muratori quoted

    Our readingWhat clean-code polymorphism really costs you is not the virtual call but the optimizations the compiler can no longer perform once it cannot see what runs.

    Their wordsBut 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.

    ↗Why performant code matters (but gets widely ignored), with Casey Muratoriyoutube.com 20th of 26 in this recording

    Interesting
  6. 3 months earlier
  7. KH

    Kelsey Hightower quoted

    Our readingYou do not have to know how it works underneath, but depth is where invention comes from — nobody who only knows the surface invents a programming language.

    Their wordsBut 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."

    ↗Kubernetes and retiring at the top with Kelsey Hightoweryoutube.com 27th of 28 in this recording

    Interesting
  8. 7 days earlier
  9. DR

    Dax Raad quoted

    Our readingIn every developer-tool category — databases, compilers, whatever — the open source option eventually becomes the default option.

    Their wordsevery single dev tool we use whether it's databases, compilers, whatever eventually the open source option becomes a default option, right?

    ↗Building OpenCode with Dax Raadyoutube.com 5th of 24 in this recording

    open source

    Interesting
  10. 7 days earlier
  11. AR

    Alice Ryhl quoted

    Our readingA compiler that names every place a change breaks turns refactoring into fixing errors until the compiler stops shouting.

    Their wordsI 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.

    ↗Why Rust is different, with Alice Ryhlyoutube.com 5th of 23 in this recording

    Interesting
  13. AR

    Alice Ryhl quoted

    Our readingRust may be the best language for AI agents to write, because the compiler gives an agent the feedback that tells it what to fix.

    Their wordsI 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.

    ↗Why Rust is different, with Alice Ryhlyoutube.com 21st of 23 in this recording

    AI agents

    Interesting
  14. 7 days earlier
  15. AH

    Anders Hejlsberg quoted

    Our readingA programming language is not a compiler but an experience: editing, running, debugging and the runtime library all have to fit together as one cycle.

    Their wordsThat 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.

    ↗TypeScript, C# and Turbo Pascal with Anders Hejlsbergyoutube.com 1st of 26 in this recording

    Interesting
  17. AH

    Anders Hejlsberg quoted

    Our readingLanguage design is ninety per cent the same work every time and ten per cent new, which is why the experience carries from one language to the next.

    Their wordsAnd 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.

    ↗TypeScript, C# and Turbo Pascal with Anders Hejlsbergyoutube.com 6th of 26 in this recording

    design

    Interesting
  19. AH

    Anders Hejlsberg quoted

    Our readingWriting state machines by hand is a nightmare and exactly the kind of transformation a compiler should do for you — which is all await really is.

    Their wordsYou 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.

    ↗TypeScript, C# and Turbo Pascal with Anders Hejlsbergyoutube.com 8th of 26 in this recording

    Interesting
  21. AH

    Anders Hejlsberg quoted

    Our readingA compiler that also serves an IDE has to be lazy and deferred throughout — a different way of building compilers from the one the textbooks teach.

    Their wordsAnd 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.

    ↗TypeScript, C# and Turbo Pascal with Anders Hejlsbergyoutube.com 16th of 26 in this recording

    Interesting
  22. 2 months earlier
  23. SY

    Steve Yegge quoted

    Our readingDeep compiler knowledge is still interesting, but it is no longer useful to a working engineer in any meaningful sense.

    Their wordsI 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.

    ↗From IDEs to AI Agents with Steve Yeggeyoutube.com 1st of 25 in this recording

    Interesting
  24. 12 months earlier
  25. TH

    ThePrimeagen quoted

    Our readingA speed difference between languages that share the LLVM backend measures the benchmark author, not the languages.

    Their wordsIt's just that Zig, C, C++, all those languages that were being tested, they're all LLVM backends, right? That's the one that actually turns the thing into the executable part. And if there's a variation in speed, it just means in one language you didn't quite express what you are supposed to correctly.

    ↗ThePrimeagen: Programming, AI, ADHD, Productivity, Addiction, and God | Lex Fridman Podcast #461youtube.com 16th of 31 in this recording

    benchmarks

    Interesting