2 ms·
As I tried to explain above, Clojure is made for a specific set of problems. Your problem seems to be interop with the SDK of the month and hiring. My problem i
by perrygeo 6mo ago
As I tried to explain above, Clojure is made for a specific set of problems. Your problem seems to be interop with the SDK of the month and hiring. My problem is mutable state. It's logical that we'd choose different solutions.
- _bypa 6mo agoA pure Clojure stack is extremely rare in most organizations. And integrating data from microservices with data lakes and observability platforms is not "SDKs of the month" but a normal business concern. What I am trying to say is that immutable state may be one aspect of something much larger that did not factor into Nubank's original decision to use Clojure for microservices. It may have clear benefits there (and in your case - I don't deny that), but downstream you pay for that rarity by having to build every integration yourself.
- uxcolumbo 6mo agoCouldn’t LLMs help with writing those glue components? Read the doc for the SDK of the month and then write the Clojure interface for it? The same goes for existing micro services, no?
- deleted 6mo ago[deleted]