3 ms·
I mean, if I've never had to maintain legacy code then my opinions on any given language are completely uninfluenced by the "honeymoon period" factor that the a
by fish45 5y ago
I mean, if I've never had to maintain legacy code then my opinions on any given language are completely uninfluenced by the "honeymoon period" factor that the article is about, yeah?
- scruple 5y agoBut they're also just uninformed about the subject, generally, no?
- fish45 5y agoThe subject is about why the stack overflow most loved programming languages tend to be recent. The article argues that because developers don't like legacy code, their impressions of languages used in legacy codebases are tainted. The subject is distinctly not about what languages are best in legacy codebases. 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
- oblio 5y agoIn the argument of which is the best pet, Guinea Pig vs Squirrel, having owned none of them, I'd also be completely "uninfluenced by the honeymoon period" of owning them as pets. But I'd probably just call myself, maybe less politely but probably closer to the truth, clueless about owning small pet rodents :-)