@jk Give someone a fish, feed them for a day; teach someone to fish, feed them for a lifetime; teach someone to think like a computer, crush them under an infinitely-growing mountain of fish.

@rk @mothcompute It happens: https://theonion.com/death-of-chopped-up-woman-ruled-a-suicide/

@cliffle @ede1998 Soo (compiler-appeasing contortions increasing to comedic levels)...

{
  let _unused = colors;
}

?

@rk Thanks, though I then regret to inform you that it was two houses ago and now quite a few states away...

@rk Well, he figured out how to scramble over that gate shortly after that photo was taken as I recall, so the joke was ultimately on us.

@rk We once were so cruel as to eat dinner on the opposite side of the baby gate from ours. Five years later I'm still racked with guilt.

@mxshift what vehicle is getting brain surgery?

@petersanchez IBM had this figured out for eSATA ages ago!

@cliffle @dpiponi Or the O(log N) operations are just really slow...like, stores are chiseling Roman numerals into stone, and loads involve OCR on an 8051 with a clock signal driven by a drugged sloth with a push-button.

@arj Shades of https://devblogs.microsoft.com/oldnewthing/20110310-00/?p=11253

@benjojo Perhaps these are the same people who added the command-not-found package to Ubuntu's default set. (Not exactly the same I suppose, but usually the first thing I torch on any new installation I encounter.)

@regehr Amsterdam might be promising: https://social.v.st/@th/113843212405715721

@david_chisnall Bowie was looking sleepier than usual this morning.

@jk @voltagex Then all you need is a way to introduce some controlled clock skew and presto, you could even adjust the duty cycle!

@cliffle Pets are great thermal photography subjects; unfortunately my already sort of camera-shy dog gets way more so when I pull out the Flir, so he's a bit hard to capture, but I did manage this one a few months ago.

@swetland I frequently find myself thinking "okay, that's it, we've saturated the scale, the world cannot possibly get any dumber than that", only for it to find a way to outdo itself mere moments later.

@jzb It seems to do that for me regardless of the console state (or anything else). It's very odd -- I see it documented, and the tooltip that pops up if I hover over the reader mode button at the right of the URL bar clearly says "Ctrl+Alt+R", but pressing those keys triggers an immediate browser restart no matter what else is going on.

[...pokes around a bit more...]

Ah -- after starting an instance from a terminal and triggering it, I see:

Crash Annotation GraphicsCriticalError: |[0][GFX1-]: RenderCompositorSWGL failed mapping default framebuffer, no dt (t=6.3471) [GFX1-]: RenderCompositorSWGL failed mapping default framebuffer, no dt

So I guess it's crashing in some special way that leads to a restart -- usually when it crashes it just dies as you'd normally expect. Clicking the button works fine though. (Shrug.)

@jzb Is this configuration-dependent or something? For me (Firefox 128.3 ESR, on Linux) it seems to just restart the browser entirely, which was...slightly surprising. (Amusingly reminiscent of classic "press alt+F4 to ..." pranks though.)

@cks @jschauma While there have probably been occasional other problems I've encountered, refusal to complete an arbitrary filename where I want one (i.e. what @jschauma described) is the most common by such an overwhelming margin that I can't think of any others offhand. FWIW, plain filename completion is bound to M-/ (\e/ in bash/readline parlance) by default, so you can usually use that to manually override obstinate tab completion when needed.

@rk I don't think I have anywhere near enough emoji in my fonts to qualify as a cool kid, but I've been running Void on my desktop & laptop(s) for about 8 years now and am generally pretty happy with it, FWIW.

@GeoffWozniak Can I ask what registrar you're going with? I'm considering transferring mine as well and would welcome any recommendations.

@GeoffWozniak Same here; the terminal performance hype of recent years is a bit baffling, though I guess not hugely surprising:

• performance is fairly easily quantifiable
• widely-used, established implementations such as xterm and gnome-terminal weren't really designed and implemented with performance as the #1 priority (because even a straightforward, non-performance-focused implementation isn't going to be anywhere close to a bottleneck in real-world use)
• implementation is complex enough to be challenging and more than a few days' worth of work, but small enough to be tractable for a single person to take on (unlike, say, a compiler competitive with gcc or clang), so it can be (or at least start out as) a fun little project to hack on

So a motivated individual can take it on and relatively quickly feel pretty chuffed at outperforming the "major players" by a substantial margin. Sprinkle in some self-promotion and that subset of the population that was doggedly running Gentoo with -funroll-loops 20 years ago and PREEMPT_RT kernels on their desktops 10 years ago and it's the pointless performance obsession du jour.

I often wonder what fraction of the userbase would actually notice if you were to sneakily replace their {kitty,ghostty,alacritty,whatever-else} binary with a build that artificially slowed it to xterm-level performance, and I suspect the answer might approach denorm territory if expressed as a float.