Clojurians Log v2

I really enjoy your podcast and I'm excited about learning / applying Clojure! I just listened to your latest podcast and I'm a beginner in the midst of learning Clojure while attempting to solve a real-world problem. I'm struggling a bit with finding examples of how I should structure my program. The program should be simple. I'm connecting to a server via TCP Socket and receiving string messages terminated by newline. When I receive a message, I need to parse it into a Clojure map, then based on the type of message, I would perform some action, then return a message to be written to the socket, or return nil if I don't need to write a message. I'm really struggling with where responsibilities should live and where or how to manage the state of the connection. Right now I'm passing around a map

{:socket socket :in input-stream-reader :out writer :config config}

@scott.archer This surely sounds like you are not exploiting idiomatic Clojure (yet). But without looking at code, it might be hard to give helpful directions.

Putting ina gist/Github repo would be nice. From whnt you described i had the feeling that this is similar to the tic-tac-toe and twitter client examples discussed in the podcast

I'll move it to a github repo. Thanks!

Is the source code for the twitter or tic-tac-toe example available somewhere?

Hey @scott.archer, unfortunately for that series, we only talked about the code

we didn't get a chance to make code available

we've used that pattern several times to good effect in non-open-source code

I listened to it. I think that's the difference in hearing and seeing.

I don't know of any examples of it in the wild

I'm hoping I can release something soon

I'm going to step back and put a "simple socket server" and "simple socket client" on github and see if I can solicit feedback / help based on that code.

I definitely understand the difference. There is nothing like being able to explore code.

cool, I'll take a look at your code and see what I can offer as feedback

Other pointed me towards the server.clj in clojure and it was very helpful.

At this point, I'm about convinced that the best way to learn Clojure is reading Clojure code.

My app is working just fine, it's just not good 🙂

I appreciate your podcast! I started listening recently and have been working through the backlog of episodes. I did listen to the latest one and it sums up why I want to learn Clojure.

When you google „clojure design podcast github“ you'll find code based on the discussions in the podcast. I cannot say anything about the quality of said code, though.

I searched that exact term in duck duck go and came up empty 🙂 google is more helpful!

Not "empty" but not with the same result

@scott.archer If your program does a lot of IO and you need the result from the IO operation to continue and the logic in-between is simple, then you essentially have an imperative program. I don't think this is the kind of program that shows the benefit of Clojure or FP in general. I would guess that the code might be at least as nice if written in e.g. Python. Another way of phrasing that is that if what you have is essential complexity, then that's what you have and it won't get nicer in pure FP. What you might find to be nicer with pure FP is the level of accidental complexity, and that will reveal itself when the program's logic grows.

Thanks @lodin.johan I've found that parts of the application are really nice with Clojure. The messages going into and out of the socket are easily transformed into maps, which makes it really easy to work with. I was looking at potentially using a finite state machine to handle the messages, but I'm not sure how well that approach will work. I'm probably just trying to use too many things I've heard about in this application.

@scott.archer Why not add some core.async go blocks to the mix then. 😉