raggi

31 ms·

451.
by raggi 3y ago
I worked on Fuchsia for about 5 years. Somewhere maybe around half way through, I think it was during a Christmas vacation, someone wrote in that they were still away from their desk, and they'd not bricked their test device, but nearl
452.
by raggi 3y ago
The conscience law, or the immigration law.
453.
by raggi 3y ago
Sadly in regions such as this beliefs and new laws are increasingly inhibiting treatments. This is a terrifying outcome in all cases but particularly with infectious diseases.
454.
by raggi 3y ago
https://doc.rust-lang.org/std/marker/trait.Send.html
455.
by raggi 3y ago
besides being slower, splitting them into two would mean they’d need to agree on abi and evolution. Having them ship in the same binary skips over those concerns
456.
by raggi 3y ago
Different than what loader?
457.
by raggi 3y ago
Let's just think this through: Google Cloud becomes a VC driven organization that slowly eats margin dirt against it's competitors until insolvency. There was no way for it to recover enough resources from the mothership before be
458.
by raggi 3y ago
That depends, the ratio of free bus capacity for data fetch, and free capacity for inter-CPU synchronization is skewed _massively_ in favor of capacity for data fetch. An x86 system is already under-capacity at the cpu/bus interface, w
459.
by raggi 3y ago
To be a little more clear on what the detail of the benchmark in question is: it’s a benchmark that explicitly exercises a pathological use case for postgresqls current design, one that nonetheless functions, and demonstrates that the adver
460.
by raggi 3y ago
It’s hard to generalize on these points. In a situation where the throughput was inverted but the proportional system usage was the same, you would instead say “you can still vertically scale by adding more disks”, rather than saying adding
461.
by raggi 3y ago
The Lindy effect applies to non-perishables. There are alternatives which are much more likely to conform to a reasonable equivalency of non-perishable for cryptography. Per this article, RSA strongly does not fit reasonable equivalent defi
462.
by raggi 3y ago
fixing the bugs is left as an exercise for the reader
463.
by raggi 3y ago
so then you do that, making stuff on the heap, doing extra zero'ing and so on, and your debug build gets faster, and you call it good. then someone profiles a release build, removes the allocation and watches the optimizer wipe out the
464.
by raggi 3y ago
argv, have the caller do it for you
465.
by raggi 3y ago
fairly straightforward: #[global_allocator] static GLOBAL: StupidAlloc = StupidAlloc; #[no_mangle] pub unsafe extern "C" fn stupid_malloc(size: usize) -> *mut u8 { let layo
466.
by raggi 3y ago
Defer has to be added manually and maintained correctly, and often has double call challenges and so on. Automatic behavior on scope exit is less fallible (including e.g. it can’t just be broken by the machine in a pathological patch applic
467.
by raggi 3y ago
Empty notepad, just started. 82,416K working set in main memory. 25.7MB in dedicated GPU memory. 59 threads. 2 billion cycles spent since launch. Two threads in !OpenAdatper12 spending ~1.5M cycles per second. Two threads in !recalloc spend
468.
by raggi 3y ago
Secure code inside the kernel is untenable. We can do ok, lots of hard work goes in to doing ok, but this isn't the kernels top priority, and never will be. Userspace is the security boundary.
469.
by raggi 3y ago
Someone needs to write "ICMP the good bits", because the traditional response of disable all ICMP isn't great.
470.
by raggi 3y ago
Oh I agree that font and weight selection are entirely preferential. In both of these images you can clearly see bad color bleed in the title bar font, and in the content font in the after case. I'm guessing the users main concern is t
471.
by raggi 3y ago
Configuring presentable fonts for the nth time was the thing that tipped me over the edge years ago to promise to myself that I will never again make another Linux desktop configuration until I see one that _out of the box_ provides a not-o
472.
by raggi 3y ago
Y’all should see the dead letters in the publish queues from dead indie servers of which thousands have gone offline but whose addresses will get looked up forevermore
473.
by raggi 3y ago
The design seems pretty wild, I have much sympathy for you implementers
474.
by raggi 3y ago
Sorry you're getting downvoted. A little dive in the original feature would reveal a bunch of unfortunate time-bombs of behaviors taking dependencies on _write time to the registry_, adding arbitrary retry loops to overcome time resolu
475.
by raggi 3y ago
one thing I can say for certain: scroll handlers definitely aren't the future
476.
by raggi 3y ago
but there are two quic quiche projects already :'''(
477.
by raggi 4y ago
Rock on!
478.
by raggi 4y ago
TL;DR Headscale is great, and we love it. Full details here: https://tailscale.com/blog/opensource/
479.
by raggi 4y ago
Yup, this is referring to GRO. IIRC we use a contiguous 64kb buffer in the first scatter-gather slot and 128 messages per syscall in the current tuning.
480.
by raggi 4y ago
Good question, it's bits and pieces. I know there's more we can do with the userspace stack - netstack has some support for GRO/GSO, but unless I'm forgetting a detail we haven't fully plumbed that yet. It would def

More ›