121 points by michaelsbradley 4 days ago | 45 comments | View on ycombinator
skydhash 4 days ago |
giancarlostoro 4 days ago |
christophilus 3 days ago |
flavio81 3 days ago |
This is the cool part. Now, i understand many Clojure libraries depend on Java libraries, so let's see how this works out for real world projects. But still, I think it's a great idea, and it's exciting. Well done, Yogthos!
On the other hand, regarding the "speaks to C", Common Lisp has had very easy interfacing to C for decades, i'm surprised this wasn't solved on the Clojure community already (!)
undefined 4 days ago |
undefined 3 days ago |
ivanjermakov 4 days ago |
So it's a matter of communication between humans. If person A is responsible for module 1 and person B's module 2 depends on the former. It's up to A to provide a proper spec to B. It's not up to B to learn everything about module 1's implementation and doing so is kinda foolish.
So something like
Is a red flag. The codebase and workflow should be that new additions should deal with a limited context (as in one PR shouldn't touch unrelated things) at at time and the contributors should be able to come with a full understanding of what they are doing. If they cannot, it's either a failure of the codebase, the docs, the workflows, or the contributors.