Fork me on GitHub
#clojure-uk
<
2018-02-26
>
maleghast09:02:02

Morning All!

jasonbell09:02:11

Morning friends

jarohen10:02:58

a request-for-comments, if I may - I've been re-thinking how Nomad (configuration library) works, after a few years of using it in various applications decided to try bringing the configuration into Clojure files as vanilla maps, which can then be generated/manipulated using standard clojure.core functions - by keeping it 'near' the code it's configuring I'm trying to avoid having to audit an entire configuration infrastructure to find out why a configuration variable has a certain value also trying to avoid a configuration library needing its own DSL for things like parsing environment variables, defaults/fallbacks, retrieving configuration from other sources, secret management etc - IME these usually turn into an almost-turing-complete language anyway - if it's Clojure, we can already use (System/getenv ...), or, merge, read-string etc

jarohen10:02:32

appreciate it's a bit of a big ask to get excited about a config lib on a Monday morning, but any feedback/thoughts would be gratefully received 🙂

firthh10:02:24

I like the idea for an environment where you’re just running Clojure services. Where you’re running multiple services in multiple languages it can be nice to keep things in a consistent state across those languages which is where you fall back to Environment variables or something your infrastructure provides like Kubernetes ConfigMaps

jarohen10:02:31

ah, yep, that is a good point, thanks 🙂

jarohen10:02:45

I've been quite fortunate to have been working with predominantly Clojure systems for a while now

jarohen10:02:23

but yes, this approach doesn't work so well in an environment with many langs

firthh10:02:00

No worries

yogidevbear10:02:34

"Lovely" snow outside

dominicm10:02:24

I loved watching it melt slowly as I waited for my bus.

yogidevbear11:02:54

@dominicm how'd your private static AWS site thing go?

yogidevbear14:02:12

Just had a penny-drop moment. I've been working with nested vectors and (into #{} ... and seeing inconsistent errors. Finally clicked that some of my vectors (e.g. [1 1]) are losing a little in the waistline (e.g. #{1})

maleghast18:02:36

Does anyone have a minute to quickly test something for me, please - will entail clicking on a link, telling me whether or not a web-page loads and then copying the top 5 lines of the page source into here for me to look at? Would also be helpful to know where in the World you are... 🙂

dominicm18:02:57

I can do it :)

maleghast18:02:06

Oh cool, thanks 🙂

mccraigmccraig18:02:37

me too if you need more than 1

otfrom18:02:32

having written a whole bunch of cross platform bash I wish I could have written that in lumo/cljs and have it play nicely in org-babel

dominicm18:02:31

Turns out cljs and node isn't that nice

dominicm18:02:39

We're moving back to clj using the clojure tools

otfrom18:02:55

@dominicm for which things?

otfrom18:02:01

for mach and things like that?

dominicm18:02:34

Yeah, for those kinds of things we're using clj now

dominicm18:02:47

With some bash glue

otfrom18:02:44

was the annoyance cljs or node?

otfrom18:02:55

(I've read some about some recent node excitement)

dominicm18:02:12

Node. The API is quite painful.

dominicm18:02:19

More, it's immature and not so well thought out compared to Java

dominicm18:02:23

There, I said it

dotemacs20:02:05

That kind of matches what I’ve seen at work. Whenever somebody needs to touch any lumo based cljs, they cringe.

dominicm22:02:37

Malcolm tends to start swearing