It's not just the ergonomics - in my head I'm moving the cursor (and with it my view) down through the document, not moving the document up. Which is mentally different from a touchscreen, though I expect people who grew up with touchscreens never built that mental association that we're moving the cursor. Fortunately Apple allows be to change it. <end old-man-mode>
Thinking about it some more, it really is about consistency regarding the cursor. On my trackpad, not in "natural scrolling" mode, I get this:
- One finger down moves the cursor down through the text.
- Two fingers down moves the cursor down through the text (moving the text up)
- Thumb-click plus one finger down moves the cursor down through the text (and selects).
in Natural Scrolling you get:
- One finger down moves the cursor down through the text.
- Two fingers down moves the cursor up through the text (moving the text down)
- Thumb-click plus one finger down moves the cursor down through the text and selects.
If you start scrolling with two fingers and release one, the cursor reverses direction! This inconsistency just really feels wrong to me, but I guess you can get used to anything.
For me it's completely different with the same result: I imagine the scroll wheel is on the paper (screen), so my finger going down rolls the wheel and the bottom of the wheel pushes the paper (screen) under it upwards.
For whatever reason this persists to touchpads even though they would seem closer to a touchscreen.
Agree about the watch - I wear a Casio LCW-M100TSE, which is also very robust (titanium case, saphire glass), never needs the battery changing and never needs setting (except for travel). But most importantly, it does what it does really well and never bugs me about anything. Downtime is important.
It seems like trucks are a use case where battery swapping would make a lot of sense. Unlike with cars, the battery doesn't need to be a structural element, and there's much less need for it to be a strange shape, as in some cars.
I'm British, but when submitting papers for blind review, always use American spelling for obvious reasons. I suppose I could change it after acceptance, but that would just be pretentious.
I've used bubblesort when simulating LEO satellite constellations, calculating which satellite is closest to a location. I used one single backwards pass of bubblesort, so O(n) every k timesteps to bring the closest to the head of the array, then every timestep just do one backwards bubblesort pass over the first few in the array. Given satellites move smoothly, if you initialize right (a few full passes at the start to get the closest few at the front) and get the constants right so a satellite outside the front few in the array can't have moved far enough to become closest without being promoted to the front few by a periodic full pass, then you always maintain the closest at the front of the array very cheaply. And this has the advantage of also being very simple to code.
