3 ms·
I think it's a bit of a mismatch when people talk about maintainability and comprehensibility, but only on very local levels, and the examples they bring up are
by threatofrain 10y ago
I think it's a bit of a mismatch when people talk about maintainability and comprehensibility, but only on very local levels, and the examples they bring up are also very local.
System maintainability and comprehensibility owe more to architecture than to local readability. It doesn't matter if local code is completely functional, or if Scala secretly uses imperative algorithms underneath. What matters is if the code module / division / unit is keeping its contract or API with respect to the rest of the system, because if it is, then you can actually hope to comprehend your system at a useful level of abstraction. Local vs system comprehensibility are not in tension, but an unfair amount of focus has been placed on local clarity.
So a question I'd have is what architectural solutions to some problem domain are natural and special to the functional style. To that end, it's more interesting to see a skeleton project tackling a generic problem, as an inspiration for a generic architecture, than to talk about whether it's possible to write locally bad code with an FP language.