3 ms·
> I can't think of any large program that has ever been forced to a drop a feature I have to anecdotes of having to drop features in a large python program due
by jose_zap 6y ago
> I can't think of any large program that has ever been forced to a drop a feature
I have to anecdotes of having to drop features in a large python program due to memory leaks.
The first one was when someone introduced an endpoint that consumed data from a gRPC service. After weeks of effort trying to find where the source of the leak was, we decided to drop the change as we could not find the cause in a reasonable time.
The second case was when introducing jaeger for distributed tracing. Similarly to the previous story, it was cheaper for us to drop the feature and use something else than to figure out where the memory leak was.
I believe that it is a matter of balancing effort vs, benefit. I would not be surprised if someone working on their free time on an open source project decides to drop a feature because they cannot find the time to make it work properly.
- dwohnitmok 6y agoI can totally believe that and have fought similar bugs (basically unexpected references that keep memory around way longer than necessary), but memory leaks of that form affect both strict and lazy languages, i.e. it's an independent problem. Lazy languages can have that same problem in addition to space leaks.