pipe_connector

6 ms·

31.
by pipe_connector 5y ago
Interesting -- how did you handle redeploys? Given that game servers are stateful (so you'd want to drain servers at their own pace instead of force them down at a specific time), it seems like redeploying a server without machinery to
32.
by pipe_connector 5y ago
I grant you that the API for capacity and length when creating a slice in Go is bad because of this exact mistake, and I believe a few of the Go authors said they regretted it and would like to change it. However, it's odd to classify
33.
by pipe_connector 5y ago
Perhaps it comes down to a difference in where we spend most of our time? I'll give you an example. I once spent a full day debugging a problem that came down to the implementation details of .zip. The author had assumed that .zip woul
34.
by pipe_connector 5y ago
I think you overestimate my ability. I've spent > 10 years programming in languages that have features like this (take and select excluded I think? Or maybe they had different names?) and I've just never internalized functions
35.
by pipe_connector 5y ago
I legitimately cannot spot the bug. Can you write out the equivalent Ruby code in Go pre-generics? I really did try but I honestly cannot understand what your Ruby code is supposed to do. I don't know what select and take are supposed
36.
by pipe_connector 5y ago
It's worth noting that the author of that article was mistaken, there was likely some other issue with their software than what they described here. ImportedLibraries() in the pe package has never done anything other than returned nil,