On Saturday, 10 December 2016 at 22:55:22 UTC, Chris Wright wrote:
It's always a bit weird when people talk about "resources" as a unification of memory, files, sockets, etc. My programs exist to fill memory and then push bits of memory around. At least 99% of my "resource" usage is heap objects. If it gets slightly harder to deal with memory but utterly trivial to deal with every other type of resource, that's a net loss.
But if your performance is hosed because you're leaking database connections, "99% of your resources" being heap objects means absolutely nothing.
