Practical use of the null garbage collector

Re:Practical use of the null garbage collector by unsnap_biceps on Friday February 07, 2025 @03:38AM (#42970638)

> He went on to point out that they had calculated the amount of memory the application would leak in the total possible flight time for the missile and then doubled that number.

I half wonder if the calculation cost more than just fixing the code.

[ Parent | on HN ]

Re:Practical use of the null garbage collector by saagarjha on Friday February 07, 2025 @04:24AM (#42970851)

Consider the marketing value of being able to tell a cool story, though.

[ Parent | on HN ]

Re:Practical use of the null garbage collector by michielderhaeg on Friday February 07, 2025 @04:36AM (#42970920)

You can make your allocations faster if you don't have to worry about deallocation. Could be a performance thing.

[ Parent | on HN ]

Re:Practical use of the null garbage collector by weinzierl on Friday February 07, 2025 @04:59AM (#42971050)

When I worked in embedded the world was sadly most often: Design and order hardware first, adapt software and requirements later.

Appeared backwards to me but in the world of mass products of extremely high quantities it makes sense to get the best hardware deals you can get month and sometimes years in advance.

[ Parent | on HN ]

Re:Practical use of the null garbage collector by joha4270 on Friday February 07, 2025 @07:00AM (#42971641)

It /does/ eliminate whole classes of errors. No use after free bugs if you never free memory.

That might have been a worthwhile tradeoff in safety-critical software where failures causes people to die (or not die as the case may be here)

[ Parent | on HN ]