Hacker News Reader

And now, reload this entire thread and check all the horrible bugs and security vulnerabilities this so called "feature" got you.

This is why you should never use C in networked code or when working with third-party data unless you absolutely bloody well have to: It's just too many ways to fuck up, and most programmers will.

View on HN

You're forgetting something about networked code. At some layer of the stack it has to be written in C or assembly.

No he didn't forget. The lower layers, yeah it probably will be in C (but it doesn't HAVE to be). But in the application layer, it probably shouldn't be.

If things like memory management are not the first priority when writing every line of code, then you shouldn't be using C, and that's really the only reason you should be using C, when there's a specific need for memory management.

Not surprisingly, this is exactly why the world has moved beyond C for the application layer, it's painful to have to think about that stuff constantly, so people just don't (this being an example).

Reply on news.ycombinator.com