ESR "Waning of Python" post
dieter <dieter at handshake.de>:
> Marko Rauhamaa <marko at pacujo.net> writes:
>> Keeping the number of long-term objects low is key.
> Right, if I need near realtime behaviour and must live
> with [C]Python's garbage collector.
Or any other GC ever invented.
> But, a web application does usually not need near realtime behaviour.
> An occasional (maybe once in a few days) garbage collection and
> associated reduced response time is acceptable.
> A problem only arises if a badly designed component produces
> quite frequently hundreds of thousands of temporary objects
> likely triggering (frequent) garbage collections.
But I think you are barking up the wrong tree. You could rightly blame
GC itself as an unworkable paradigm and switch to, say, C++ or Rust.
Or you could blame the parts of the software that create too many
You shouldn't blame the parts of the software that churn out zillions of