she/they
- 0 Posts
- 25 Comments
2s in firmware??? I’m used to at least 30s
Do you get two empty spaces next to your tower? For maintenance if the lower elements.
It’s called a tower PC for a reason
True, but we’re not talking about clear and up front rules
I’m not the person you’re replying to, but I am stupid enough to occasionally get close to falling for a scam. Rather than test my luck, I’d rather they didn’t exist.
Pick something and change it when inspiration strikes. Sometimes you need a big picture view of something to get the right abstractions or even just name things.
Indentation implies there’s some control structure causing it. Too many control structures nested gets hard to mentally keep track of. 3 is arbitrary, but in general more indentation => harder to understand, which is bad.
All human strings are finite…
Green threads are functionally the same, especially in languages that can preempt.
You really should be doing your IO async. Do you specifically mean callback hell?
Steam OS is completely open source except for the Steam client.
They do, I was joking. It’s not as funny to say the ecosystem is slowly trudging along.
Wayland compositors might implement it this century
4·8 months agoMaybe there’s a signal handler or some other outside force that knows where that variable lives on the stack (maybe through DWARF) and can pause your program to modify it asynchronously. Very niche. More practical is purely to inhibit certain compiler optimizations.
It makes more sense if you think of
constas “read-only”. Volatile just means the compiler can’t make the assumption that the compiler is the only thing that can modify the variable. Aconst volatilevariable can return different results when read different times.
4·9 months agoI believe POSIX mandates grep and a shell that should be able to handle everything this code uses, but sudo is a problem
I think my BIOS has a setting to skip that part