😼 mogge

@dominicm I guess in some places it hasn't that much, see @agile_geek

- another day, another non working development environment....never mind I'm off Friday and Monday so only today and tomorrow to survive!

learn you a haskell is a good read @agile_geek 🤓

I left my copy at home!

and access internet is difficult to say least

I've got post conference fatigue syndrome

Morning all

Sounds like a tough day in Clojure UK land. From non-working dev environments to PCFS 😉

@otfrom really? Do you have family up there?

nope. My wife got a job at U Dundee as a research fellow

Congrats (I hope)

Are you going to be commuting down to the offices in London?

Or managing entirely remotely?

a bit of both. We're well set up for remote

Sounds like a good balance

When does the move happen?

Do people have a preference or rule of thumb of where you put colls in function args? i.e. at the start or end of the arguments, I guess it depends what the function does. I can vaguely remember seeing some sort of article/text about this sort of thing

General rule of thumb: the thing you're operating on goes in the first argument

As a big regret to clojure, map, etc. take it as final argument, so if you want to use it with e.g. ->>, put coll you're working on as last

(I’ve had connection “issues” this morning - it’s raining torrentially and it seems to play havoc with the microwave transmitter…)

@dominicm eh, clojure is consistent in this regard and there's a reason for things being in first arg vs last arg

the phone line drops at my parents when the wind changes direction.

@bronsa I thought Rich had said he wished it was the other way round? I know coll is consistently at the end, which is good. But there's no consistent, "always first".

the functions that take coll as a first arg operate polymorphically on collections, the functions that take coll as the last argument operate on sequences

see the difference between e.g. update/conj/assoc and map/filter/remove

[off-topic] Anyone else see this: http://spectrum.ieee.org/computing/software/the-2017-top-programming-languages There are some surprising results in there, at least in my opinion…

I tend not to take too much notice of those kinds of lists.

lol @ "clojure - an attempt to revive lisp by making it compatible with the same vm that supports java programs"

and "haskell - designed for applications where reliability is important"

very hard to measure these things IMHO. the one thing that would make sense to measure I guess would be value vs. cost of code created in X language. but no idea how to do that.

Yeah, I tend to take them with a pinch of salt (or indeed a bag full), but that Python should be at the top was quite the shock…

…and considering the academic bias of the source I thought there would be more functional languages higher up the rankings too…

academic bias = python, no? SciPy is a winner.

I suppose you are right there @dominicm - just had not really thought it through there…

https://clojure.org/guides/threading_macros

@yogidevbear moving in September

Makes sense. For the start of the new academic year, yes?

@otfrom - Congrats on the geographical upgrade 😉

thx 🙂

:flag-sco:

😕

Hold on….

There we are @otfrom - sorted…

(I named the flag “saltire” so that when the St Andrews Saltire is added to the International emoji-spec :flag-sco: will still work… 😉 )

😄

I ❤️ that you can add your own emoji to Slack

🚆 :flag-sco:

nah not quite 🙂

🚆

better 🙂

👍 👍 👍

I feel like I've missed something along the way. Can someone explain to me?

means !

Ah! Thanks for clarifying that @mccraigmccraig 😉

sigh...

in our slack it is :hug: