I think the idea here is: how do you write as many 1s as you can - without going into an infinite loop. You gotta stop. You only have 10 states in a state machine to "program" with.
That's BB(10).
The naive way to solve this is to generate all possible 10 state state-machines and see what they produce - take the biggest one.
Except many of those will go into an infinite loop - and you cannot easily detect that (or detect it at all for arbitrary n - see also: halting problem) so you go into an infinite loop too.
> the fact there are two pointers on the screen -- one for the mouse and one for the keyboard -- if you slide the mouse pointer to a specific point and press a keyboard key, the new key will not appear where the arrow is, it will appear where the text cursor is.
I remember using an (early?) Apollo computer that worked that way... I was warned by the person showing me, and a bit later he accidentally bumped the mouse while I was typing! Letters all over...
I believe this was in the era before X windows took off for unix boxes. I miss SunTools - it was nice and simple.
Focus follows mouse was a thing in the X11 era too. We are still in the X11 era, and it is still a thing. (-: Until X11 window managers like IceWM vanish entirely, it will remain a thing.
I think of focus-follows-mouse as a different thing. FFM raises the window under the mouse, but doesn’t move the text insertion point (at least on X and Windows, the only two places I can remember using it). But the Apollo’s window manager was different - moving the mouse moved the insertion point along with it.
but raising the window under the mouse also, for "true" FFM, gives kbd focus to the raised window, which will in turn (via whatever GUI toolkit is being used) moved kbd focus to some widget in the window, if possible.
It is impossible to generalize about this under X Window, since the behavior is entirely controlled by the window manager, and their behavior (a) varies (b) is very customizable.
I had personal subscriptions to WebStorm and GoLand and cancelled them not long after getting Windsurf. Just don't need the IDE abilities like I used to... Still use 'go to definition' but that's pretty much it.
As a resident of an independent living facility, I live among a lot of people who use various makes and models of powered chairs. And a great many who have the joystick dislike it immensely, and would prefer to have the handlebars-style navigation. But it's kind of the only way to have the "chair" style, nothing in front of you design. Some of the more scooter-style have rotating chairs, so you can park parallel to a table and turn, but that depends on lower limb mobility, so no easy solutions here.
The "climb a 13° slope, clear a 2-inch curb and cross a 4.7-inch gap" is quite impressive.
it writes to the file with elevated priviledges and doesn't write it back to the terminal, effectively a 'sudo sh -c '{cmd} > {file}''.
sudo tee is a common way to work around priviledge restrictions in shell pipes (you can't easily 'sudo' a pipe), if /secure was 0600 and owned by root:
"sudo echo "test" > /secure" or "sudo printf '' > /secure", would not work because your user's shell process can't write to /secure. However, "echo 'test' | sudo tee /secure" works because the elevated 'sudo tee' can write to the file.
A few that I looked at are annotated, "It is linearly stable (largest Floquet multiplier 1.000), so a small nudge only makes it wobble." Doesn't define "small nudge", alas...
I use it, and have been happy with it for the most part. Like sibling, I use it for GPT-5.6-Sol and Opus work, and use their free models (GLM 5.2 for the past few months, trying SWE-2 now).
