This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-10-11
Channels
- # beginners (57)
- # boot (9)
- # clara (9)
- # cljs-dev (12)
- # clojure (98)
- # clojure-boston (1)
- # clojure-dusseldorf (12)
- # clojure-france (1)
- # clojure-greece (1)
- # clojure-spec (41)
- # clojure-uk (86)
- # clojurescript (60)
- # code-art (2)
- # data-science (5)
- # datomic (5)
- # duct (1)
- # fulcro (14)
- # graphql (2)
- # lein-figwheel (4)
- # luminus (1)
- # midje (1)
- # off-topic (19)
- # om (10)
- # onyx (13)
- # pedestal (5)
- # portkey (59)
- # re-frame (31)
- # reagent (1)
- # ring (14)
- # ring-swagger (1)
- # rum (5)
- # shadow-cljs (90)
- # spacemacs (5)
- # specter (47)
- # sql (9)
- # uncomplicate (95)
- # vim (32)
@dominicm you might need to unpack that a little for me (I’ve not had my water yet)
@peterwestmacott I think I strongly associate yankee with texas area rather than Americans generally.
do they eat ribs for breakfast in Texas?
https://letsgostealaleverageblog.tumblr.com/post/162396829573/exactingleverage-the-studio-job from a tv show I watched
Leverage is a great show if you enjoyed e.g. Hustle btw. Slightly different. It even had a recurring Wil Wheaton character 🙂
Leverage was great 🙂
@dominicm - You know that Texans are the very antithesis of Yankees, right? Texas is on the Southern border, is a bastion of “The American South”. The Yankees are the Northerners…
Oh really? Does that apply to "Yankee Doodle" too @maleghast?
Admittedly people outside the US often apply the term to all Americans, but if you called a Texan a Yankee they’d likely as not punch you in the face 🙂
Morning 🙂
The song, Yankee Doodle, goes back to the Civil war -> https://en.wikipedia.org/wiki/Yankee#Yankee_Doodle
Morning @yogidevbear 🙂
How is everyone doing this morning?
All good, thanks, here in Balham… I am in London ‘cos there were supposed to be investor meetings… The investor meetings are next week (I will be back), so I am “working from home” from my AirBnB… At least it’s quiet… 😉
I'm working from home in the London library because it takes 3 weeks to get connected to the internet in this country
@cddr it's taken 11 years for me to get a half-decent internet connection, and i live within 50 miles of london
Two different slack groups and both talking about internet speeds this morning lol
That's some synchronicity for you
what did you try to set it to @glenjamin?
doh, now i see it 😊
I could tell you a joke about UDP, but you might not get it.
"Hi, I'd like to hear a TCP joke." "Hello, would you like to hear a TCP joke?" "Yes, I'd like to hear a TCP joke." "Ok, I'll tell you a TCP joke." "Ok, I will hear a TCP joke." "Are you ready to hear a TCP joke?" "Yes, I am ready to hear a TCP joke."
No, you didn't 😂
2) Ordering There are 3 hard problems in computing: 1) Naming things 3) Cache invalidation 4) Off-by-one errors
6) mismatched parentheses?
Hell, I tried parinfer and it found a load of bracket/indentation errors others had made that noone had ever noticed...
it was more a comment on the n)
style of numbering - an attempt at humour if you will
yes - paren matching is a job for machines
[dear future robot overlords, I mean simpler machines than you]
@otfrom Hi. I'm using still using paredit. I haven't moved on to more modern stuff.
@nomiskatz do you use terminal Emacs? Looking for some tmate paredit solutions for c right arrow and friends
How often do you guys use pmap
?
Rarely. It's usually the wrong solution to a problem.
I mean, it's very convenient. But it's sort of a sledgehammer.
Usually better to do something with core.async or executors so you have more control over the concurrency etc.
That said, when we were getting started with Clojure at work (2011) we fell in love with pmap
🙂
I can see the initial appeal, but I can also see it being overused as a novelty
And what about future
? https://clojuredocs.org/clojure.core/future
Yeah, we still use future
a lot.
Mostly for fire-and-forget stuff, where we know we won't overwhelm the system.
But we also use it when we have a fixed set of long, complex DB queries that we want to run concurrently (and, again, we know the DB server can handle it and we just want to cut the overall elapsed time).
One thing to bear in mind with future
: it swallows exceptions by default. We use timbre/logged-future
instead, so at least we see exceptions in the log file.
Cool, thanks again Sean 🙂
on the same lines manifold/future
has callbacks so can play nicely with your other promise-like things
@yogidevbear pmap
doesn't really do what most people expect it to do. See eg https://dev.clojure.org/jira/browse/CLJ-862
claypoole (https://github.com/TheClimateCorporation/claypoole) has a version of pmap that has more intuitive behaviour.