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.
And that kind of compiling of information about the materials is something other fields do that we don't do. An analogy that I would think of in software would be something like a 500-page book on how to version an API.
Some people think CI means you reject grammar books. I disagree. I often reference grammar materials and find these explanations useful. However, the focus of my learning is not to “master the rules”. Grammar resources simply help me notice and make sense of patterns in the language.
the ballerina and the kind of performer, that's the wrong reference class. Right now we have a lot of jobs where you have different tasks. So this is the task-based model jobs where you have like a lot of different tasks. So like a doctor, what is their job? They're filling out insurance documents. They're you know, going and like calling different pharmaceutical companies. And one of their tasks is to actually see the patient and talk to them, but that's like actually not the main part part of the job.
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."
LLMs themselves are the perfect captive reader: they never get bored or confused, never miss a reference or have an emotional reaction, never ask themselves why am I reading this?, never close the tab.
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.
And what this is is that in the guide level explanation, you explain your feature as if you were writing a guide as if the feature already existed. And in the reference level explanation, you explain your feature again as if it already existed, but as if it would be in the language reference instead of a tutorial.
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.
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.
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.
AI today it's just starting to to become aware of you know the existence of of of language services and agents today like to use grep and awk and whatever you know to to find all the places where you reference a certain thing but it's not semantic search, right?
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.
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.
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.
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.
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).
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.
The big flaw is that it's justified through a fictional world. It's not justified through reference to the real world. It's not empirical in a way. It's not... Rand herself would say this. She's not writing about things how they are, but how they should be. That idealism just really undermines it as a mechanism to understand where we're actually living.
So very important to keep in mind that Rus is not Russia because that was a self-name for all multiple groups on that territory. And Moscow doesn’t exist at the time when Kyiv emerges as the capital. The first reference to Moscow comes from the 12th century when it was founded by one of the Kievan princes.
The Linux Programming Interface by Michael Kerrisk – an exhaustive reference on how Linux works. There are about a million chapters, but every individual chapter is pretty short and I find it quite readable.
I use Roam as my main note-taking app. While I only use very basic features such as bidirectional links and reference blocks, it works well enough for me.
I was disappointed. I love Tim’s work, but this didn’t deliver in the way his past books have. There’s zero thematic organization, so you can’t reference certain topics you want to learn more about except in a few cases. While this has some interesting pieces, I doubt I’ll refer back to it like I have with Workweek, Body, and Chef.
not only did I buy the canonical reference (The Rust Programming Language by Steve Klabnik, Carol Nichols and community contributors), I also bought an O'Reilly book with a bit more narrative (Programming Rust by Jim Blandy and Jason Orendorff).
I take my hat off to Hugh. This is one wine reference book that I have nothing to do with, and it is absolutely brilliant. It's very small—although, of course, it's been getting bigger and bigger as the wine world has expanded—and it does pack a heck of a lot of information.
Other frequently used programs include Dreamweaver and Fetch for my site; Chrome, iPhoto and Preview for reference hunting; iTunes, Spotify, and Downcast to keep me company.
The book is colorful and ludic which is a good idea for a "Beginner's Guide". The layout is attractive, there are many detailed examples. I like the pedagogy: the author wants you to learn by doing. However, the book is poor as a reference: the coverage is limited despite the 300 pages and the chapter summaries are strictly non-technical.
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.