4 ms·

I think one thing that this post touches on is the effectiveness of Java as a programming language for large projects. I agree that Java has its uses, but I've

I think one thing that this post touches on is the effectiveness of Java as a programming language for large projects. I agree that Java has its uses, but I've always thought that this was one of the weaker ones. Java's poor syntactical support for clarifying abstractions like lambdas or rich data structures like hashmaps makes small projects larger than they need to be. The answer isn't to find a way to manage large projects; it's to find a way to make them smaller. Size is poison, and automated refactoring is no cure.

waps 13y ago
Size is poison, true. Not nearly as much as, say, dynamic typing. At that point you start having the exact same code mean different things at different times. Plus those analysis tools you have for java do help with complexity. That always baffles me. People get frustrated with java's verboseness for a large project ... and switch to ... python or ruby. Those languages require ridiculous amounts of discipline to work well in large projects (and needless to say, said discipline tends to be absent in the vast majority of developers).