Morning And welcome @wesley.hall

moin moin from a very cold and windy Rotterdam....

Mornings!

Random core function of the day:

-------------------------
clojure.core/set-validator!
([iref validator-fn])
  Sets the validator-fn for a var/ref/agent/atom. validator-fn must be nil or a
  side-effect-free fn of one argument, which will be passed the intended
  new state on any state change. If the new state is unacceptable, the
  validator-fn should return false or throw an exception. If the current state (root
  value if var) is not acceptable to the new validator, an exception
  will be thrown and the validator will not be changed.

Morning everyone 🙂

morning

I'm starting to get feeling back in my toes

I'm not sure I want this

Morning.

Not really clojure related (but definitely “thinking about software” related), I have so much respect for this:

https://twitter.com/levelsio/status/938707166508154880?lang=en

I think those are so few and far between though, no?

Not you say that's not impressive!

Of course. I’m not advocating either for PHP or for a 4,500 loc file being the whole app. That’s horrible. But it’s a real point in favour of ruthless pragmatism - this guy knew how to write an app with a single monolithic php file and he shipped it, and now it’s working for him. I can’t not respect that.

Welcome @wesley.hall 👋

It's 4500 loc?

Woah

@chrjs @dominicm - Indeed, got to offer a hat off to that achievement...

Yeah, something of that order. The comments on the tweet are a maelstrom of opinion, naturally.

I wonder if a library would have been much quicker...

There's some things which are repeatable.

Probably. I don’t think the moral here is that a 4500 loc PHP file is the path to product success. I just tip my hat to the reverse attitude: “Yeah I could have learned Laravel. While you do that, I’ll just be here making a fortune on the dumbest thing that might work.”

Sometimes #jfdi is the best course of action.

For sure. There's a definite scale here.

I think I have a large distrust of myself, and lean on libraries to be repeatable ways to get things right.

Does anyone know of an easy way to add custom encoders to pr-str?

With clojure.edn/read-string I can pass custom :readers, but for the writing part I’m scratching my head.

(obvs. I can tree-walk and manually encode things, but that seems a little sub-optimal)

@peterwestmacott you can extend print-method

@dominicm I think that desire to lean on libraries to get things right is one of the main differences between clojure and other lisp cultures (and why so many of the old c.l.l crew dislike clojure)

“c.l.l” ?

maybe common lisp language?

didn't know cancer patients had such strong opinions of clojure

comp.lang.lisp on usenet

which is one of the worst programming communities I've ever had the misfortune of being involved in

it’s not even as bad as it used to be now

people have written long posts on how common lisp helps antisocial people create big systems without having to co-operate w/anyone and thus it attracted those kinds of people

back when erik naggum was still alive and xah lee was active — “fun” times

I won't use any of Xah's stuff b/c of how he was there

same w/Erik

There are politics EVERYWHERE, huh? *mind blown*

there’s this nice blog post by dr tarver about that type of community http://www.shenlanguage.org/lambdassociates/htdocs/blog/bipolar.htm

The hard problems are often people-problems.

mmm... the smell of blowing away your elpa dir in the afternoon.

good way of testing to make sure my install code still works. 😉

“elpa”? - is that an emacs thing?

emacs lisp package archives

@otfrom - What's MELPA then..?

https://melpa.org/#/

Milkypostman's ELPA

Modern..? More..? Moderately Interesting..?

obviously

😉

Milkypostman - yes of course, that should have been clear to me from the beginning...

Thx though 🙂