Hacker News Reader

The language just gave you a block of memory. It lets you decide whether you'd like to dedicate resources to clearing that memory.

Ok, so for what is usefull to have garbage after get memory?

Why do I need to zero an image array if I am about render something into it? You spend time setting each byte to zero.

That, and when your constructor is going to initialize every field, and when you're going to clone a copy of another structure...

I understand if I get null/empty... but garbage?

And in relation to this post, the behaviour is not the same across compilers/archs? Thats nuts.

Welcome to programming in the real world. If that's the nuttiest thing you have to deal with on any given day, it's a good day.

Yep, I know programing is hard. +18 years of it.

Is crazy the amount of punishment a developer accept, and when the fail is elsewhere, it blame itself ;)