Comment by kamma4434
4 months ago
That’s my top issue with Clojure: I see what the function does, but is it expecting a list, a string, either, or a map? The function may apply correctly, but what was it supposed to do? Java may be boring, but it’s surprise-free. In Elixir this is less of an issue because of pattern matching and very clear errors showing the actual arguments passes, that are unbeatable for debugging - you look at the log and can “see” the issue.
In Clojure you typically program to interfaces/protocols and not to types
The Clojure docs should be more straightforward about the interfaces that are available and targetted
You can still have a problem of not knowing which is required of an argument, but its usuallt clear contextually
What I mean is that it is harder for me to reason about. In Java you also use collection interfaces, but List<String> is a no brainer.
yeah, your overall point stands. Sometimes you can get a bit mixed up on "wait, does this take a File object or a string with the filename?". I guess my point was that because you program to interfaces this happens a bit less often than one would expect. If it can take a vector it can usually also take a list