λlain.bit retweeted
ALGUÉM TEM CORAGEM DE JULGAR ESSE GUERREIRO??
Brasileiro de 22 anos morre em combate na Ucrânia; família tenta repatriação de soldado ao Pará glo.bo/47TjAqg #g1
one of the reasons why having two mutable references is UB in Rust is that the compiler perform optimizations under the assumption that an &mut reference is the sole path to that memory for as long as it exists
λlain.bit retweeted
Que a alma deles esteja com Nosso Senhor.
Victim of doomed Florida plane heard reciting Lord's Prayer before jet crashed, killing all onboard trib.al/bhKeUrK
λlain.bit retweeted
Quem pulou carnaval sabendo da COVID e o parente morreu depois, tá bem preocupado com a própria culpa. É mais fácil culpar o presida mesmo.
λlain.bit retweeted
Rezem pela alma dele.
λlain.bit retweeted
Após reeleição de Lula, Ministério da Justiça censura 'desenhos bíblicos' da Record
oantagonista.com.br/ladooa/a….
λlain.bit retweeted
Typescript compiler notes.
github.com/microsoft/TypeScr…
λlain.bit retweeted
Writing an OS in Rust (by Philipp Oppermann): os.phil-opp.com
λlain.bit retweeted
When I applied to Microsoft in 1992, I'd read that they received 100,000 resumes a year.
I never did hear back.
I'd been selling HyperCache for the Amiga to put myself through college, so I did what any reasonable person would do. I went through every customer registration card looking for any microsoft.com emails. Email was rare enough already (my first Microsoft business card would have a Telex number but not email).
Only about 3 people had microsoft.com email addresses, so I cold-emailed each one.
One fellow, Allistair Banks, wrote back. And the rest flowed from there. Without his reply, it never would have happened.
We lost Allistair a couple of years ago. Until then, I emailed him every couple of years on my work anniversary to thank him, though!
Much as Steve Jobs owes a debt to Bill Hewlett, I owe a big one to Allistair. And like Jobs, I've always found that if you ask someone for help genuinely, you quite often get it.
λlain.bit retweeted
There is so much wasted RAM, wasted CPU & bloated code in the world, you wouldn't even believe it
I'm a single engineer and I'm mediocre so I'm doing what I can to clean up human slop code but the amount of it throughout the world's software is overwhelming
There are hundreds more examples in this project alone, imagine how many there are in every other library used by your computer...
And these are just optimizations, there are also hundreds of bugs and security flaws everywhere
I was asked to look into optimizing ffmpeg's nnedi algorithm, which Jacky uses to restore old video footage
So I ran a few Claude threads to look for inefficiencies, and it found some bloated code
My PR was merged today:
51 lines added
120 lines deleted
Up to 51% lower RAM usage
Simpler logic
Same output
Same CPU usage
Now that RAM isn't wasted and the code is simpler, I can work on CPU optimization
My problem is that, out of nowhere, I get an urge to dig all the way down to see how something works internally.
For example, I see the "Inspect" option in the Chrome context menu, and I end up tracing it all the way down to the Chromium C++ code to find out where it’s actually implemented.
to perform identity mapping of virtual addresses to 4gib of physical addresses, 2048 2mib huge page directory entries are required.
x86 long mode checklist
- [ ] enable CR4.PAE (bit 5) (physical address extension, 36 bit physical addresses)
- [ ] enable EFER.LME which indicates the intention to enter long mode
- [ ] load PML4 page table into CR3
- [ ] enable CR0.PG activating pagination
- [ ] the cpu is in long mode at compatibility mode, still executing 32 bit instructions because the current code segment has L=0 in the GDT
- [ ] perform a far jump to a code segment with L=1 in the GDT