I also stopped reading the article there. This is major version 4 of a library about providing higher level db actions, i.e. transactions are paramount to make them atomic
Sorry to be blunt, but if you don’t want to spend effort on touch typing (and therefore avoid arrow keys), learning vim motions is rather pointless and you might as well not bother.
I just looked up the compression rate of FFV1 because I never thought about this. It’s apparently 4x. More would be possible, but increase computational requirements.
Another use cases seems to be archival of historical footage.
I don’t think that you guys should be debating compressed vs uncompressed, but lossy compression vs lossless compression. Your math seems to derive from a naive storage format.
I’d still use a byte slice for that. Some formats may mix encodings, or have a text header and binary payload. For those cases one would need to use memchr for the first byte, then compare the remaining few bytes. So I don’t think it would be a huge performance impact
For context, initial WoW was developed until 2005, and up to roughly 2003 Blizzard was going to release it only for the US and Korea, because they thought “Europeans only play racing games” (source: WoW dev diary by Staats)
1. Make individual agent AIs that can act on their own.
2. Make squad AIs that can influence their agent AIs.
3. Add even more AIs on top, like a scenario AI.
Each of these AIs can be a state machine, behavior tree, rule system or goal system. They’re exactly equivalent and can be translated into each other mechanically. So the whole hierarchical AI is equivalent to one big state machine.
I started to learn Japanese 30 years ago, and in my experience the people who try to be smart and build systems almost never get decent. It’s procrastination while thinking they’re actually productive.
To add insult to injury this article hasn’t discovered anything new, makes it sound way more complicated than it is, and in the end still requires you to just remember which verbs are of the eru/iru group, and which are not (which was posed as a problem to solve in the intro).
Just make cards and mark the stem, learn it along with the verb. No need for heuristics. If you ever forget, you’re bound to remember the masu-form and can reverse engineer the stem from that 100%.