3 ms·
I can't agree ... BASIC was an extremely productive language, and so is Perl, but both are a terrible bet in the long run due to debugging/maintainability/reada
by lazyjones 14y ago
I can't agree ... BASIC was an extremely productive language, and so is Perl, but both are a terrible bet in the long run due to debugging/maintainability/readability issues. Being able to throw new code at something isn't everything, unless you plan on throwing it all away after 5 years in favor of the next fad.
- rubenv 14y agoWorks both ways really, people might hate your project because you stick to old & known C, rather than write it in e.g. Go.
- lazyjones 14y agoGo is a great language for maintainability, much better than C. So it would be a good choice and arguably quite productive too.
- rubenv 14y agoThat's sort of not the point here. It's not always that "new fad" is better than "old and established", it might be the other way around. What matters is what's most productive for the project, for the people working on it. What doesn't help is making a fuss about it. Spend your time contributing and get over the fact that not everyone thinks the same. Or walk away, because nobody is forcing anyone to get involved. Let's just stay constructive and respect what people are doing. If you really want to do it differently, just go out and do it, prove people wrong with results, rather than arguments and flames. That way everyone wins.
- Nursie 14y agoDo we have any long term case studies to that effect yet? Is C inherently unmaintainable in your opinion? Or just badly written C?