Fork me on GitHub
#clojure-uk
<
2016-07-28
>
korny14:07:33

insightful convresatio here today

dominicm14:07:20

I love weavejester's comment, I wish I saw more code like it.

dominicm14:07:56

> I absolutely second the advice of using CQRSish replayable system architectures, and Onyx is really great I thought this one was really interesting. Especially as it's my current interest in software.

glenjamin14:07:36

> The small pain at the beginning and the minor inconvenience of git submodules saves a world of hurt later.

glenjamin14:07:49

i’m on board with extracting libs that have clear interfaces - but submodules 😖

glenjamin14:07:01

At work another team decided to start using submodules, about a week later: > This is on hold as we do more testing in preventing users from mistakenly overwriting each other's submodule hashes in the parent repos after this has happened recently

agile_geek14:07:29

Yeah, I remain unconvinced about Git submodules

minimal14:07:39

They can be useful but I wouldn’t plan to use them

thomas15:07:51

ok clojure question… I have a massive map (from a rest API) and I want a small map with just a few of those key/value pairs in it

thomas15:07:00

what is the best way to do that?

thomas15:07:29

I know I can do

map :state {xxx xxx xxx xxx}

thomas15:07:49

to get a single one… but can you do something like an or on that?

glenjamin15:07:13

is it nested? select-keys sounds relevant if it’s flat

thomas15:07:23

no, nothing nested

thomas15:07:29

ooh let me have a look

thomas15:07:58

that looks like it… never seen that one before!!!

thomas15:07:05

@glenjamin: that function did the trick. Thank you

korny16:07:17

Reasons to like clojure … part 3 …

korny16:07:53

And this will make the type purists scream with pain I suspect - but this is in largely disposable Jepsen tests.

korny16:07:43

I have a module for testing ActiveMQ, which uses a bunch of classes like org.apache.activemq.ActiveMQConnectionFactory

korny16:07:53

And I have a module for testing Artemis, the likely replacement for ActiveMQ, which uses a bunch of classes like org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory

korny16:07:00

(this is a poor example as both of these do share a common interface, but I have others that are not so friendly)

korny16:07:39

basically I can cheat and rely on reflection to talk to these, where they have methods in common but not interfaces in common.