3 ms·
I have looked at many production java codebases. I agree that some things can be complex, but that is typically a feature of a framework (java has many configur
by ecshafer 5y ago
I have looked at many production java codebases. I agree that some things can be complex, but that is typically a feature of a framework (java has many configuration heavy frameworks) and not the code aspects. But I haven't seen any production code that is complex simply because it is production java.
Could you give an example for your point?
- Twisol 5y agoI've seen an internal Java-based web application (a digitization of some business processes involving what used to be paper forms) in which nested elements in a web page corresponded with subclasses in Java. Way high up in the hierarchy, it had `HTML`, `CSS`, and `JavaScript` classes, each of which eventually descended from a `Document` class. It was impossible to properly trace any behavior through. Every method zigged and zagged through the inheritance hierarchy multiple times as you traced deeper. And so: > It is (no matter how verbose or clunky) still easy to read and understand. The sentiment is taken well, but it's just not true. Credit your fellow engineers for the positive experience, not any particular language.