Hacker News Reader

It would not trigger the same bug.

But since it's a multi-threaded server, it will exercise arbitrary code (Rails core, your app, depended-on gems) in a concurrent manner.

This can unmask race conditions that wouldn't manifest themselves under a single-threaded environment.

...that's been my experience with Puma - brilliant server in itself, somewhat risky approach when considering the Ruby ecosystem.

nope. puma does the right thing. this is exactly what i looked at when i saw unicorn in the article

I thought Github at one point looked at Puma and decided not to switch over. I wonder if they will reconsider that now.

to be fair, switching over is probably non-trivial and/or risky

This is what I'm going to be digging for later... I'm wondering if puma also shares `env` objects across requests.

Each server does share a "proto env" object, but it is duplicated for each Client:

and Client objects are not reused: