There was a movie about Tom Cruise running in Docker:
Spotify is in the process of trying to monopolize podcasts. watch how the pathology plaguing the whole American tech sector play out in real time. if they're successful, in a few years most podcasts of note will only be delivered through Spotify and they'll start using their dominance to do horrible shit
Nice explanation why invalid code that is "unused" can still cause problems:
(spoiler: because compiler optimizations reorder code and can make unused code in fact used)
Apparently browsers GC handling can sometimes integrate knowledge of which events can and can't happen.
Haven't confirmed this across browsers (yet), but means otherwise awkward tracking can be avoided. It also probably explains why some very common idioms around XHR and Promise don't leak memory. Which I never thought they would anyway, but didn't really know why.
Every HTTP request library needs to support connection timeout, response timeout, etc. to prevent app from hanging in poor network conditions. Merely an "abandoned" request could still sit wait forever, wasting memory.
Except in async #Rust, which has an interesting model: when you stop polling a Future and drop it, it explicitly aborts everything it has been doing. So if the app gives up on the request, it will get cleaned up automatically even if it was stuck. No need for special timeout API.
this list is complete; you can help by shrinking it