More likely these companies just offered to give them some free vending machines and some office manager said sure why not. Not everything is a careful corporate strategy.

Yes, but the important distinction is that its intention is to bring people together face-to-face, not isolate them to their desks for continued work. Just because the end goal is "productivity" broadly speaking, doesn't mean the mechanisms are socially/morally equivalent.

> I doubt anyone is forcing the employees to take the stimulants.

I agree, and I hope my comment didn't imply I thought that was the case.

OTOH, if you've witnessed how most managers talk about their employees to one another, it's with a cold calculating language. Sure, a manager may feel bad for firing an employee, but first and foremost is the business analysis of whether it makes sense to do so - just pure math and predictions.

Personally, if I was in a management position and an employee asked me for a cigarette, I would happily give it to them. In fact, a few times a week I give a few cigarettes to 1 person who is not my employee, but who I talk to from time to time. I don't gain anything from this and I give them cigarettes because they are on a tight budget.

Also, if I, as a hypothetical manager, realized a lot of my employees would take an offer for free coffee, cigarettes, pure nicotine, beer or another drug, I would give it to them as long as it didn't hurt productivity too much. Of course some drugs like alcohol could hurt short term productivity, but it would make them happier overall, which would have positive long term effects. If asked why I do this, I would say that I'm both giving them out of my good will and to increase productivity, which would be true.

Trying to blog more frequently with shorter posts!

firefox's reader view helps too

You mentioned, "E.g., in OP, memory is leaked on allocation failures." - Can you clarify a bit more about what you mean there?

    const recv_buffers = try ByteArrayPool.init(gpa, config.connections_max, recv_size);
    const send_buffers = try ByteArrayPool.init(gpa, config.connections_max, send_size);

A) clean up individual allocations on failure:

    const recv_buffers = try ByteArrayPool.init(gpa, config.connections_max, recv_size);
    errdefer recv_buffers.deinit(gpa);

    const send_buffers = try ByteArrayPool.init(gpa, config.connections_max, send_size);
    errdefer send_buffers.deinit(gpa);

    const recv_buffers = try ByteArrayPool.init(arena, config.connections_max, recv_size);
    const send_buffers = try ByteArrayPool.init(arena, config.connections_max, send_size);

    const recv_buffers = ByteArrayPool.init(gpa, config.connections_max, recv_size) catch |err| oom(err);
    const send_buffers = ByteArrayPool.init(gpa, config.connections_max, send_size) catch |err| oom(err);

    fn oom(_: error.OutOfMemory) noreturn { @panic("oom"); }

The allocation failure that could occur at runtime, post-init, would be here: https://github.com/nickmonad/kv/blob/53e953da752c7f49221c9c4... - and the OOM error kicks back an immediate close on the connection to the client.