HN user

eska

1,728 karma
Posts0
Comments766
View on HN
No posts found.

I don’t know zig syntax, but wouldn’t it be possible to put this common pattern into a macro and simplify it to mostly a lambda on V?

In Germany there’s private insurance which can only be chosen by people of higher salary and good health because the rate depends on their condition when they sign up. So this data would be biased towards sick people, people doing jobs that are more likely to make you sick, and people who are financially less well off.

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’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)

That is still simple AI and commonly used.

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%.

I mean that mostly in the sense that there is huge variance in idiomatic code. So your optimized C/Rust code might be 100-1000x faster than two idiomatic versions of writing that code

I appreciate that you first tried to optimize the original Python code. Idiomatic Python is unfortunately disappointingly slow and not so interesting to compare to.

There is no “zero” immigration policy, this is a strawman. Controlled immigration is different from opening the floodgates.

Also weird to admit that no country has reversed its birth rate problem, but still insist upon massive immigration being the solution.

I keep hearing this argument on HN. Yes, if performance is something you care about you totally look at the disassembly. You don’t even need to write assembly, just be able to read it. By now I assume that programmers who argue they don’t need to understand and review what the LLM generates for them are simply not that skilled and don’t realize that skilled programmers do this.