ulbu
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.
- 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
https://www.fortinet.com/resources/cyberglossary/data-securi...
https://en.wikipedia.org/wiki/Data_security
https://www.nccoe.nist.gov/data-security
etc
all of these start with “unauthorized access” to define this term. can you please explain how open access to private repositories is not unauthorized access and how you can’t expect your data moving to private repositories to be private?
and ternary is a branch with no variable introduction, so it doesn’t apply again.
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.
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.
zig is on its way to improving compilation times in its own pace and does so for the benefit of the project and everyone involved, so what is left to care for about bun by anthropic’s past?
the efficiency should come with future releases that are expected to provide a solution to this “dispatch still dynamic, even though comptime-known” problem.
stack traces are esoteric and error messages entirely unhelpful,
documentation masquerades as deep but is indeed inconsistent and prosaic, mixing styles of reference, explanation, and how-to willy-nilly, (compare with Dybvig’s The Scheme Programming Language, which is focused and consistent, and it takes no time to get your answers; there’s just no method to guile and guix manuals), i hate it big time,
there’s big gaps in documentation (especially with Guix – there’s literally zero information about `define-record-type*` which is used everywhere in its codebase; admittedly, not scheme related, but still),
the cli requires too much memorization,
most modules are not named, but numbered, ie, instead of something like `(base list)`, you get `(srfi srfi-1)`, so you need to either memorize, or go through the info pages for each procedure you need to import, which means you also need to know the exact names for the procedures you need beforehand,
there’s like 4 ways to define a record, each with a different feature set and incompatibilities,
etc.
these are the reasons i find it hard to use.
to respond to the content of the article, the different neurotype idea is off, because scheme allows you very well to express sequences of operations; the ecosystem of APIs may not cater to this tho. although if it was rephrased into “scheme emphasizes symbolic manipulations, as opposed to operating a machine”, i would agree
edit: thanks for the responses!