ulbu

because it’s much further away. if you have your desktop adapted to be keyboard-driven, things that are far apart in 2d space may be very close in logical user-event space. same holds here. moving a single finger and clicking usually requires much less movement. and movements compound.

and your observation is not at all universal. moving a vehicle is much easier via a mapping to a more abstract control, as opposed to controls resembling the effector. this abstract control also fits many vehicles. the same is true for all sorts of controls.

- map aisle sequence of your store to numbers

- prepend each entry with aisle number

- sort by number

- remove aisle number

or, of course, you can outsource your brain, it might turn out to be less resource-expensive

calling what someone else finds interesting “not an interesting measure” is itself something that calls for an interested measure.

but zig has no ternaries, so it does not apply to a discussion about zig’s syntax.

and ternary is a branch with no variable introduction, so it doesn’t apply again.

(it’s basically a weak switch expression, and the value moves leftwards towards its invocation.)

if |result| (evaluation)

|capture| hides an inconsistency that bugs me – everywhere else, assignment to a variable flows leftwards. |capture| is an unnatural rightwards assignment.

in general, I like zig syntax, but i find that it had very little regard to how the eye moves on the page. it’s jarring at times.

I think they mean red as a shell scripting/command line language.

or “sometimes not, until more data arrives”.

it’s little-endian protocols that require that you juggle your struct fields.

plus, there are still big-endian protocols that will stay for a long time. for example, MIDI clip files in MIDI 2.0 are big-endian.

C3 is a contender to C++ because of its namespace operator?

you need different packed structs for little- and big-endian data. and casting with little-endian data is a nightmare - you need to reverse-cascade your struct fields to be in accordance with the little-endian bit-pattern. (or have a comptime function that does it for you, of course. but then you lose all declarations for the struct). what should be a simple writing down of a protocol is now a pedantic and error-prone ordeal.

well, it doesn’t say Lua5.1-JIT