[ceol]

> You've turned something that's a person's fault into something that's the language's fault.

> You're taking a look at other people's code, and judging the language from it.

At some point, you have to start blaming the language for fostering an environment where that code is acceptable.

[blackhole]

Meanwhile, people still manage to write memory leaks in garbage collected languages specifically designed to not leak memory.

[Retric]

GC is not about preventing memory leaks, it's there to make managing memory easier not automatic. One of it's biggest advantages is the ability to deal with memory fragmentation which is ridiculously hard to do well in C++ style languages.

[jsaunders]

You can write bad code in any language. It's the programmers responsibility to make sure the stuff they are writing is good and that only comes from experience with the language.

[PyErr_SetString]

Of course you can. But is it always an equal share of bad code for each language? If not, then you have to admit that the language itself will encourage or discourage bad code or bad coders.

[chaostheory]

It's easier to write bad code in certain languages, as well as vice versa.