A perllsp process (written in Rust, I think?) went rogue overnight and consumed about 500 GB of RAM, making my Mac very unhappy. (No time to debug it, so I uninstalled it.)
In QE, the Treasury issued long-term bonds. The Fed bought up the long bonds, issued overnight debt, and passed the interest difference back to the Treasury. In the end, it is just as if the Treasury issued overnight debt in the first place.
I would say, sometimes, I don't know if it's controversial, that very few developers understand memory management. And that makes it even harder to debug memory problems. And so the state of the art around memory debugging hasn't evolved all that much over the years.
To shout “temporary” and pull the plug essentially overnight after immigrants have relied on the government’s representations that they should put their efforts and future into establishing a life in the United States wreaks unfair havoc on the lives of immigrants as well as the welfare of their communities.
Right now: llama3.2:3b appears to be the model for: is this email urgent?qwen3:8b appears to be the model for: summarize this 5000-word article. llama3.3:70b(q8) appears to be the model for: let’s write or debug some computer code.
and I don't think we're headed to that world largely because of the fact that the models rely so much on large scale test time compute in order to achieve um their greatest intelligence. If you if it requires so much test time on compute to unlock the full capabilities of the model, then that means you're bottlenecked by time
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 I've gotten to a certain point and I thought it was like fairly well tuned and then I let auto research go for like overnight and it came back with like tunings that I didn't see.
the average athlete who's taking a few million dollars more to move his wife and kids from one family, one city that they loves him and that he loves to some strange place where everybody's going to be unhappy.
I go back to usually when people are unhappy it's because these things are a little bit out of sync. Like they want this big thing, but they don't actually they're not actually excited about what it takes to do that thing and therefore it's just going to be a mismatch.
One performance anti-pattern is when a company, to debug one performance problem, installs a monitoring tool that periodically does work and causes application latency outliers.
I’m unhappy with that. I would not be happy with information loss. I love that it’s telling us that there’s this crisis because I do think it’s giving us the clues, and we have to take them seriously.
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.