Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Type safety is a lie. Everything is a piece of memory. C does not hide this from you, it's a design feature and not a bug.


> Type safety is a lie. Everything is a piece of memory.

So speaks an Assembly developer

> C does not hide this from you, it's a design feature and not a bug.

I guess the design goal was to make security exploits as easy as taking caddies from children.


>> So speaks an Assembly developer

C is a portable, readable assembler abstraction in a lot of ways, yes. I'm not seeing what's wrong with that. Was that supposed to be an insult?

>> I guess the design goal was to make security exploits as easy as taking caddies from children.

Do children often have caddies? I've never noticed a child with a caddy. Golfers perhaps.

I'm still not sure why you think type safety is the be-all and end-all of everything. You can have memory violations and leaks just as easily in type-safe environments as any other. There are lots of ways to f*ck up in C, but the flexibility turns out to be useful as well, when used appropriately.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: