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.
When agents write code, you don't always need a full sandbox. You can 𝚛𝚞𝚗 their code in a lightweight QuickJS secure context. Faster and more cost-efficient.
Um, but actually the median business, uh, is doing better this year than a year ago. Um, and so and then if we kind of, um, stratify and look at the probability that any given business will reach some revenue threshold, a million dollars, five million dollars, 10 million dollars, whatever, um, those all seem to be getting better.
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."
A Hawbuck wallet. I still use cash, so no aluminum thingy or phone add-on in place of a wallet. It's not made of animals, lightweight, lasts a long time, not that expensive, a perfect wallet.
Finally, I tried these extremely cheap ones, and they were best of all. $13. They're perfect. Solidly built, lightweight, great sound quality, what more can you ask for.
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.
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.
So that's unfortunate, and that's why some environments like Go, for example, has has Go routines and green threads, which are really language emulated lightweight threads that kind of do what I'm talking about, but but at a much lower cost. But you avoid the function coloring. So there is a bunch of different things, but but you know, but for an environment that already exists like JavaScript or like C# and and the Windows event loop and and whatever, this this was the right solution.
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.
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.
Away is my go-to brand for durable, quality luggage. Their hard shell carry-on suitcases are lightweight and fit perfectly into overheard bins, ensuring you have plenty of room for all your gear while still letting you travel carry-on only.
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.
Small day pack. A lightweight pack is great for carrying a sweater, camera, guidebook, and picnic goodies while you leave your large bag (with most of your belongings) at the hotel.
The logical end state of this displacement is not some hybrid grid with around 20% solar backed up by spinning generation, but a much more dynamic, versatile grid with around 200% solar generation and hours to days or weeks of battery storage, fully decoupling time of generation and consumption.
Image is perhaps the most versatile format for model inputs, as it can be used to represent text, tabular data, audio, and to some extent, videos. There's also so much more visual data than text data.
At home, I'm usually working with one monitor (laptop) so I use a laptop stand to not have to bend over. I invested in the Roost a while back. It's a bit overpriced, but lightweight and does the job. Now, I might look at one of the competitors if I were to buy one today.
I use VS Code as my primary editor mainly because it’s more modern, highly configurable, and lightweight in comparison to other Electron-based editors such as Atom.
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.