This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-04-26
Channels
- # announcements (1)
- # atom-editor (7)
- # babashka (9)
- # beginners (46)
- # cider (1)
- # circleci (2)
- # clj-on-windows (1)
- # cljdoc (5)
- # cljsrn (2)
- # clojure (25)
- # clojure-austin (8)
- # clojure-brasil (4)
- # clojure-europe (52)
- # clojure-nl (1)
- # clojure-norway (162)
- # clojure-uk (2)
- # cursive (3)
- # datalevin (134)
- # datomic (16)
- # defnpodcast (8)
- # graphql (9)
- # honeysql (5)
- # hoplon (26)
- # hyperfiddle (18)
- # introduce-yourself (1)
- # lsp (4)
- # malli (19)
- # nbb (16)
- # nrepl (1)
- # practicalli (3)
- # releases (3)
- # shadow-cljs (36)
- # tools-deps (7)
- # vim (2)
- # xtdb (9)
@UK0810AQ2 I regret not considering this earlier, I might have tried to submit a talk or so. But I bought a streaming ticket to console myself...
@U04V5VAUN Looking forward to meeting you! I'm en route right now at 33,000 feet 😁
Somehow I thought they they looked like an alien space ship and the bins are a transmitter
What type of camera are you using @U04V5V0V4?
Here in NL we have green for garden and food waste, blue for paper and grey for the rest.
I’m mostly posting from an iPhone 14 Max Pro with the odd filter @U0K1RLM99
@U052852ES I haven’t checked the local ordnances, my bad 😂
@U04V5V0V4 definitely lovely for an iphone photo. No idea what control you have in camera. I only ever use a phone camera selfies with @U0525KG62 🙂
I also have a Nikon Z5 and tried my hand at HDR merging this evening. I think I have some better shots but this already seems OK.
The Z5 is an excellent camera, I have a friend who has one and she loves it. I seem to have become a camera storehouse. Most things I do are on a Fuji X100, I have a couple of Nikon D300s, an old Fuji S5 Pro and a Sony HX60 for keeping in the car, just in case. 🙂
Just ordered the telephoto converter for the X100 🙂 Got my eye on a couple of 6x6cm TLR cameras as well. And then there’s the guitar pedals 🙂
Yeah but you don’t need it though do you @U052852ES 🙂
måning
I miss Slack threads in Teams. Maybe I'm just not doing it right yet.
I think if you need threads in Teams, your best bet is to create a Team in Teams and use that for chats instead of direct messages.
At the customer I work with we use Teams and have chats for team group chats, and that doesn’t work very well in my opinion.
Thanks 🙂 We're scrambling to figure out how to use it best.
@dominicm been doing some work with async interceptor chains ... so i revisited IOC (again), 'cos it made a nice 'other' use of the interceptor chain - https://github.com/yapsterapp/slip
You know you can theoretically create an asynchronous parallel start function over Component?
the async thing is mostly about an async factory referring to objects created by another async factory... i.e. effectively chain
ing the promises to create the DAG
Component does that by accepting a walk function that by default just calls the start method, but you could theoretically "join" all async return values
am i missing something - looks like a regular reduce
- https://github.com/stuartsierra/component/blob/master/src/com/stuartsierra/component.cljc#L130 ?
well, after topologically sorting it's equivalent to a walk, but I'm looking for a blog post about starting components in parallel, it had an example
agree - the difficulty i would see with starting components in parallel (presumably sub-trees of the dependency graph) would be that you could get a whole DAG of simultaneous error conditions - you could ofc unwind sensibly, but presenting what happened sounds quite challenging
might be worth it if your system is taking an age to start though
our prod system does not take an age to start, so i've never really worried about parallelising