dinn - Network

KDE Plasma was my go-to but after a third computer switch and having the exact same workflow-killing issues i had 2 years ago it grinds my...

KDE Plasma was my go-to but after a third computer switch and having the exact same workflow-killing issues i had 2 years ago it grinds my patience more and more

in the meantime when i'm on windows this aspect feels great. the rest of the OS doesn't of course

it seems my choices are always between a bad attempt at being windows or a completely different beast that basically feels like vim but it's...

it seems my choices are always between a bad attempt at being windows or a completely different beast that basically feels like vim but it's the whole OS (which is cool, but i'm not the target audience)

i'm sincerely disappointed of the state of the linux desktop environment world. i can't enjoy any of em without a huge "but" to water it...

i'm sincerely disappointed of the state of the linux desktop environment world. i can't enjoy any of em without a huge "but" to water it down

guten morgen

guten morgen

i need to understand a really specific thing about nm (from GNU binutils) and i have to deal with a 2100+ LoC file looking like this

i need to understand a really specific thing about nm (from GNU binutils) and i have to deal with a 2100+ LoC file looking like this

why do people use obfuscators for their code when they can just format their code GNU-style

why do people use obfuscators for their code when they can just format their code GNU-style

the Tesco bootloader is doing numbers again

the Tesco bootloader is doing numbers again

web development

web development

made 80 cents buying items for a key on backpack.tf and selling it for more than the price of a key on the steam marketplace

made 80 cents buying items for a key on backpack.tf and selling it for more than the price of a key on the steam marketplace

i end up missing { get; set; } from C# more often than i would have thought

i end up missing { get; set; } from C# more often than i would have thought

i have mistreated you for too long, css grid

i have mistreated you for too long, css grid

random old post from April getting attention for no reason

random old post from April getting attention for no reason

trying to understand the inner workings of FreeBSD through the official docs is almost impossible. yet i still trust the docs more than any...

trying to understand the inner workings of FreeBSD through the official docs is almost impossible. yet i still trust the docs more than any paper or article talking about the Linux kernel inner workings

hola

hola

https://youtu.be/B8xHWwCuxKA?si=gjj-SS7ksAm7nD1z

https://youtu.be/B8xHWwCuxKA?si=gjj-SS7ksAm7nD1z

this is being extremely picky, but I'm sad that I can't use the system as-is to handle awaiting for a job in a fiber contexti guess...

this is being extremely picky, but I'm sad that I can't use the system as-is to handle awaiting for a job in a fiber context

i guess I can still do some trickery by having a macro secretly turning an async function (job) back into sync code by turning every .await into what the fiber system wants to see but that's like meta programming on top of a already very complex fiber system. quite a pain

to be fair as far as safe rust (and 99.99% of scenarios) is concerned, it's literaly the best solutionI only know one scenario where the...

to be fair as far as safe rust (and 99.99% of scenarios) is concerned, it's literaly the best solution

I only know one scenario where the state machine becomes dead weight and of course it's fibers

fibers do not need a state machine to store where we are in the function since they save the stack pointer and program counter. jumping back into it is literaly just a "jmp" asm call, no branch needed

having async functions creates a Future object that internally manages a state machine and has it's own quirky way to handle local...

having async functions creates a Future object that internally manages a state machine and has it's own quirky way to handle local variables (i might want to look more into that)

this is very, very, very low cost (no allocations, no runtime, ...) but I would not call it zero cost. some specific scenari that could benefit from the rust async await syntax would actually have to pay the price of this state machine, without having to use it

I'm pretty sure "rust async/await is a zero cost abstraction" is a false claim

I'm pretty sure "rust async/await is a zero cost abstraction" is a false claim