This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-02-23
Channels
- # admin-announcements (1)
- # announcements (1)
- # beginners (222)
- # boot (210)
- # cider (26)
- # cljs-dev (50)
- # cljsrn (19)
- # clojure (243)
- # clojure-art (12)
- # clojure-finland (1)
- # clojure-poland (43)
- # clojure-russia (46)
- # clojure-sg (13)
- # clojurescript (60)
- # core-async (14)
- # css (11)
- # datomic (9)
- # devcards (9)
- # dirac (2)
- # editors (13)
- # emacs (5)
- # euroclojure (1)
- # events (3)
- # hoplon (76)
- # immutant (10)
- # job (1)
- # jobs (2)
- # keechma (1)
- # ldnclj (33)
- # lein-figwheel (1)
- # leiningen (20)
- # luminus (26)
- # mount (31)
- # om (105)
- # onyx (56)
- # parinfer (29)
- # perun (12)
- # proton (1)
- # re-frame (14)
- # reagent (5)
- # sydney (1)
- # yada (15)
is core/async deterministic enough to use for low-latency games?
I could just try it of course
yeah I'd be curious to know how it works out for you. timeout
resolution is 10ms at the moment
I don’t know if I’d use timeout for anything fine-grained
I’ve been playing with some little games in Clojure
just using a “classic" game loop, but I could see something like core/async being very useful for coordinating AI and such
having multiple independent control flows going without coordinating threads would be great
I needed/wanted a clock signal with better accuracy than timeout so I wrote a timer-chan that uses the j.u.c scheduler
works pretty nicely with core.async; mediates with a dropping buffer, so if work takes longer than a tick for whatever reason, you just skip ticks
interesting
so it puts a value on the chan at a regular interval?