kgadek

Depends on what are you doing. For any programmer working on a bigger project, where compilation time is greater than 2s, (let's say) 4x more power is superb.

If your code compiles in ~16 seconds, reducing that to 4 would add comfort.

If your code compiles 60 seconds, reducing that to 15 would allow not losing concentration.

If your code compiles in 60 minutes, reducing that to 15 minutes would actually allow to do any work on that (not that it's not possible, but it's really not pleasant).

MongoDB + Haskell.

Something I hate with passion and something I love with passion. This makes me cringe…

  Q: Why Python?
  A: The only alternative would be Haskell, but I still have to learn that.

Possibly (dunno). But they refer to that on slide 7:

    -  We also introduced new safer APIs like reallocarray()
    -  I wrote a big diff for nginx to adopt reallocarray() other such techniques
    -  And it got rejected.

I feel that it's getting more common recently.

…I'm not pointing in any direction… ducks