but i rather ask a question. ive nooticed Chrome freezes its processes when they bump into a memory limit. that means it is C++ exceptions. Java throws an exeption too. Go goes into panic. so the question is why is it considered correct behaviour to throw an exception? why not merge/multiplex a memory error into other errors returned normally?should the modern runtime (parts of it) descend to exceptions only when user-developer screws the logic or supplies retarded inputs? why gramps decided to die on memory?
i thought.. whata heck, why not just loop forever, making an allocation a never failing op - this requires an operator, say, he closes a tab that cosumed 500Mb, memory arrives, allocation succeeds and process "unfreezes" naturally without exceptions and without using OS API for complicated freeze/unfreeze mechanics..it can be kinda opt-in feature of memory allocator. other approaches possible..
i can never tell anymore if i'm out of the loop or this is just a schizo's loop i've found myself in
