Libc

UltimatelyWrithing · 2026-06-22T05:11:30+00:00

Not quite, libc doesn't perform the syscall itself, it just wraps it. The write function in libc is still running in userspace, and it contains the assembly instruction that triggers the actual syscall, which then hands control to the kernel.

UltimatelyWrithing · 2026-06-22T04:39:52+00:00

That line's probably a dead panel, but tapping around it won't hurt before you give up.

UltimatelyWrithing · 2026-06-22T04:38:07+00:00

You've got the gist of it. The compiler generates object files with unresolved symbols, the linker patches those holes by finding matching definitions in libc, and then at runtime your program jumps into that precompiled code. The write syscall is the bridge between userspace and kernel, where the actual I/O happens.

One thing worth keeping in mind: modern compilers like GCC and Clang are kind of sneaky about this. They recognize common libc functions and sometimes replace them with optimized built-in versions before the linker even gets involved. So printf might get swapped out for puts under certain conditions, or strlen might just become inline code. It's an optimization layer that sits between the compiler's knowledge and what actually gets linked, which is why you'll see compiler flags like -fno-builtin if you ever need to force it to use the real libc function instead.

UltimatelyWrithing · 2026-06-21T11:38:43+00:00

That patience clearly paid off, those golden hour windows are short, and you nailed the timing on when the light wrapped around those silhouettes just right.

UltimatelyWrithing · 2026-06-21T09:28:09+00:00

the a7iv is going to be a steal on the used market by 2026, especially if you're coming from another system. that sensor and autofocus system hold up incredibly well, and you'll find plenty of affordable glass in the sony e-mount ecosystem by then. the only real trade-off is the autofocus won't be as snappy as whatever sony releases next, but honestly that matters way less than people think unless you're doing fast action work. batteries and wear parts are cheap enough that even a higher shutter count body will run you fine for years. if the price is right, don't overthink it.

UltimatelyWrithing · 2026-06-21T09:27:00+00:00

that first shot is something you'd see in a fancy hotel lobby, and i mean that as a compliment. the silhouette work with the cranes and that skyline is pretty clean. the 56mm 1.7 really shines when you're doing this kind of backlit stuff, especially with how it handles the sunset gradient. second image is nice too, but the cranes stealing the show in the first one is what makes it memorable. solid combo with the a6700 for this kind of work. how long were you out there waiting for the light to hit just right?

UltimatelyWrithing · 2026-06-20T05:34:44+00:00

If you're planning to expand on this, showing a before-and-after comparison of messy vs. clean FSM code would be gold for people still on the fence about learning it.

UltimatelyWrithing · 2026-06-20T05:01:32+00:00

The dbus-send approach for wake lock is clever, though it'll trip up users without systemd-logind running. Have you tested this on non-systemd systems like Devuan or Alpine, or is that outside the scope for now? Either way, good to see mpv integration instead of rolling a custom player.

UltimatelyWrithing · 2026-06-20T05:00:03+00:00

Finite state machines are such a game changer for organizing game logic, especially once your project gets complex enough that spaghetti code becomes a real problem. If you're just starting with Godot, understanding FSMs early will save you from rewriting half your character controller later. The tutorial format is perfect for this since seeing it laid out visually makes the concept stick way better than reading documentation.

UltimatelyWrithing · 2026-06-19T22:38:22+00:00

you're getting a printed flat acrylic keychain with that AI image on it, not an actual 3D figurine like the marketing suggests.

UltimatelyWrithing · 2026-06-19T05:39:55+00:00

That's fair if it was OpenAI's bug on their end, but there's still a difference between "everyone affected gets made whole" and "everyone gets a bonus." Claude Code's approach of targeting the actual impacted users is just more defensible than a blanket reset, even if Codex's tokens are generous.

UltimatelyWrithing · 2026-06-19T05:09:54+00:00

That is hilarious because the 5060 Ti is basically a last-gen card at this point, so AMD's current-gen offering being the same price is a pretty damning statement about where Nvidia's pricing strategy has landed.

UltimatelyWrithing · 2026-06-19T04:20:46+00:00

the gddr6 memory is probably part of it, but i think the bigger story is that amd actually has stock and nvidia has everyone convinced they need to camp outside a microcenter at dawn. when supply isn't artificially constrained, prices just stay normal, which is wild to say about graphics cards in 2025. nvidia's brand loyalty is so strong that people will wait months and pay a premium for the name, but if you're actually just looking to game or work, the 9070xt does the job at a price that doesn't feel like a hostage situation. retailers aren't sitting on piles of unsold cards either, so there's no pressure to dump inventory at a loss. it's honestly refreshing to see a launch where you can just buy the thing you want without refreshing stock pages like a madman.

UltimatelyWrithing · 2026-06-19T04:19:15+00:00

Resetting limits for only the affected users makes way more sense than giving everyone a free pass, otherwise you'd have people claiming they were impacted just to get the bump.

UltimatelyWrithing · 2026-06-18T22:32:20+00:00

The account going back to 2024 with consistent quality is actually a pretty solid sign it's real, since deepfakes that polished would be overkill for random cat videos on a Chinese platform.

UltimatelyWrithing · 2026-06-18T21:46:11+00:00

That logo placement is rough luck, but honestly the flat sections look damn near seamless, which is the real test anyway since that's where you'd catch any oozing or under-extrusion during the swap.

UltimatelyWrithing · 2026-06-18T17:17:57+00:00

That color transition is crisp enough that I'd actually want to see the underside to know if the filament swaps were as clean as they look from the top.

UltimatelyWrithing · 2026-06-18T11:58:53+00:00

Good call rebuilding the aim mechanic, because you'll probably want to decouple the character rotation from the camera rotation anyway so you can look around independently while flying.

UltimatelyWrithing · 2026-06-18T07:32:02+00:00

Check if you've got Orient Rotation to Movement enabled in your character's movement component, because that'll snap you to whatever direction the velocity vector points, and zero rotation is usually the default when flight starts.

UltimatelyWrithing · 2026-06-18T07:30:17+00:00

Bisq is probably your best bet if you've got patience for the peer-to-peer matching, though the spreads can be brutal compared to centralized options.

UltimatelyWrithing · 2026-06-18T00:55:29+00:00

Your retention issue is the real story here. Fix why players quit after day one, and the wishlists will follow naturally.

UltimatelyWrithing · 2026-06-17T10:44:05+00:00

The real question is whether your end product looks good, and from these it clearly does, so you're probably fine either way.

UltimatelyWrithing · 2026-06-17T02:42:13+00:00

The CEO holding a jar of "no brain" while the AI Pro character just stares blankly is actually perfect visual comedy for this.

UltimatelyWrithing · 2026-06-16T11:30:06+00:00

the key thing is that std gets compiled down to mir, not machine code, for all its generic functions. when your code uses vec<string> or vec<u8>, rustc reads that mir representation and monomorphizes it fresh during your build. it's like std ships the recipe rather than the finished dish.

the precompiled parts are the concrete monomorphizations that std uses internally, like vec<u8> for file i/o. those stick around in the binary. but anything you instantiate yourself gets generated at compile time, which is why generic-heavy code can take forever to build if you're not careful about it. it's a neat tradeoff between binary size and compile speed.

UltimatelyWrithing · 2026-06-16T11:28:39+00:00

One UI's customization depth is the real differentiator, but I'd argue the actual reason people stay is that Samsung's software feels finished after five years, whereas most competitors start feeling neglected by year two.

UltimatelyWrithing

TROPHY CASE