> I've never had to maintain legacy code before
If you didn't mistype your comment, it's super funny.
So in a discussion about programming languages and software maintenance, you comment saying that you've never had to maintain legacy code? :-))
If you didn't mistype your comment, it's super funny.
So in a discussion about programming languages and software maintenance, you comment saying that you've never had to maintain legacy code? :-))
But I'd probably just call myself, maybe less politely but probably closer to the truth, clueless about owning small pet rodents :-)
But since we were discussing about what the best way to raise them so that they avoid most old age diseases, I guess that takes us to square one :-)
I have written code in many of the languages on the list, green or brown, and in a few of them I've worked with large codebases not written by me. I wouldn't consider any of them legacy though since they're fairly recent.
I am also a person, so I have preferences about the languages I write in. These preferences are exactly what stack overflow polls about. Because I have not worked on any legacy codebases, my impression of brown languages has not been affected by working on legacy code.
The fact that I, as a person who responded to the stack overflow poll who generally prefers green languages to brown languages, am unaffected by the factor that the author presents as significant, is an anecdata in opposition with the author's argument.
It's true that I'm uninformed about working on legacy codebases, but that's not the subject that my initial comment addressed