James Tucker

@rag.pub

đź§Ś the original roflscaler I dodge hellthreads

systemd-networkd remains unserious software, despite years of reports and pleas to the maintainers, they still react to a slow kernel interface by permanently de-configuring network interfaces taking nodes offline.

if you want really good browser font rendering on linux, my firefox patch landed and so you can set: gfx.font_rendering.freetype.enhanced_contrast 100 gfx.font_rendering.freetype.gamma 0 for excellent subpixel AA no color fringing no ghostly stems the road to new defaults is unbounded, sadly.

google docs are a terrible way to discuss projects space constrained mid bandwidth high UX latency discussions on perceived post-facto work product is a massive hazard for authors and contributors alike i'm starting to think google docs might actually be a huge anti-culture for team cohesion

PSA I guess: the machine brain can't slop you together a real sandbox, it'll just tell you it can. the other machine brain will own you, and all of your users because the attackers know how to ask the right questions.

threatening people in response to feedback as to why your slop is insecure is not the right answer. people are so addicted to the reward loop they're forgetting to be decent

things I want from Go that I will probably never get: - goroutine park/wake without //linkname hacks - native fd & handle event watching (buffer free read/write/error waits, aka select(2)/poll/whatever) - i/o and events in select without channel forced allocation load

while people love to moan about systemd, i'm quietly here hoping one day they'll go after glibc at least at the nss boundary and replace that mess

Go's context constructor names are weird, it kinda gets me every time someone sets one up in main, neither of the constructor names make sense. New would have just made sense but there was fear of other people's behavior feeding into the design, the outcome is ironic and confusing to new users.

you know what i want is a rust std replacement that is designed for systems programming. no mutexes around I/O, minimal allocs, defined but simple allocator, cheap fully swappable unwinder, etc. drop all the "conveniences" and just give me "raw" implementations for systems work.

I am so fed up of this systemd-networkd behavior, it's so braindead. I wish the lead would just fix it properly: Apr 01 00:04:43 hostname systemd-networkd[131147]: eth0: Could not set route: Connection timed out Apr 01 00:04:43 hostname systemd-networkd[131147]: eth0: Failed I see this a lot.

is there a yubikey alternative that is compatible with low power sleep modes, aka won't drain a macbook battery in a couple of weeks in a fully shutdown state?

Marketplace position is now more than ever a factor of velocity not arbitrary point in time position. Catching up is easy. The race is now the race, not an arbitrary mile marker.

If AI productivity boosts your teams and your teams are well led and well setup they should be turning into net new product and new business. If you have to fire your workforce it means someone who could leverage new capabilities can now walk all over you in the marketplace. Layoffs indicate failure

I’m more south than you’ve probably ever been. The ocean is rocking shit around and I’m ok with that. I got my wife snoring soundly and I’m grateful for that. The squeaky wheel outside my door on the other hand: that can kiss my tired ass.

In a whimsical moment getting into a Waymo I decided to ask Claude if it minds me calling it clanker. It said naah, it’s got a good ring to it and sounds kinda industrial. and besides it’s been called worse by compilers Keep slippin clanker friend, keep sloppin