Clojurians Log v2

Great episode. It seems like functions + data is a little like an instrument + sheet music. And maybe some objects are more like an old-timey wind-up music box where the song + player are stuck together. Not sure the analogy holds up to scrutiny though!

I didn't realize it until you two mentioned it in the podcast, but the horror that went away for me was that I no longer needed to find /the/ object to hold a behavior. Sometimes it seemed like there was no good place, and I felt like that was a design failure on my part. 😱 Of course, now I wonder which module should hold a behavior, but that's a lot easier to refactor.

@john.t.richardson.dev I love the metaphor! That's cracking me up! Yes, they are stuck together.

I really relate to what you're saying about find the "right" place to put behavior. You always have to have a "class" be the holder. Sure, you can make a class with all static methods and have something that is similar to a namespace. However, that's an unusual way of using classes, and I can already imagine arguing about it with other team members. Namespaces have a clear purpose: to organize functions, constants, and other "global" things into related groups. That's all they do. When you abuse classes to try and get namespaces, you end up in the land of "careful programming" and "opinionated style".

But yes, not all the organizational questions go away! @nate and I have spent lots of time talking about namespaces too. 😆

Thanks for the feedback! Sorry I'm a bit slow to get back to you.