logoalt Hacker News

Jolt – Clojure that speaks C

90 points • by michaelsbradley • yesterday at 4:23 PM • 27 comments • view on HN

Comments

christophilus • yesterday at 11:34 PM

Well, I think this looks nifty. Yogthos appears to be the author, and he’s done a lot for the Clojure community over the years. I’m definitely going to give this a spin.

giancarlostoro • yesterday at 7:10 PM

Curious how it compares to Jank which is also Clojure but for C++.

https://news.ycombinator.com/item?id=50202762

https://jank-lang.org/

➕ show 1 reply
skydhash • yesterday at 6:40 PM

Was initially interested (I like languages that binds easily to C because of the nice libraries there, and I'm a fan of LISP), but the README is LLM-generated and the Makefile is unreadable. The there's this part in the AI policy

  It is simply not feasible for humans to keep the entirety of large projects in their heads all at once. When working on a project, one is constantly forgetting and relearning code along the way. The situation is even worse for projects where multiple people work together and no one knows what everyone else was thinking. We look at the code and try to build up sufficient context in our heads to make the necessary changes. When we misjudge that context or misunderstand existing code, we end up making mistakes.
It's a made up excuse because no one has ever tried doing that. Instead the core activity of software engineering (and engineering in general) is to break down things into modular components, ensure that they work well, produce specs, then assemble the result. Which is why no one read the source code for open(2) system call before using it. Instead they read the manpage and only when there's an issue there's a need to compare the specs with the implementation.

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

  Any new code that is added is therefore always done with limited understanding.
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.
➕ show 2 replies