Really cool stuff @petecorey
danbruder
paulsullivanjr
outlog
this one is particularly awesome and inspiring (even though I don’t play any instrument)
reminded me of this talk, where a drum machine is built : (code: GitHub - mtrudel/beats: Beats is a drum machine · GitHub)
so just making sure you have seen that one..
petecorey
Yes! That’s hands down one of my favorite Elixir talks. I’m actually using SchedEx in another side project, thanks to that talk.
OvermindDL1
kelvinst
I liked the way SchedEx is configured, seems a lot cleaner than Quantum. And also, the time_scale modules look really amazing. 
slashdotdash
GenServer’s handle_call/3, handle_cast/2, and handle_info/2 natively support sliding timeouts. You don’t need to write any custom code.
handle_call/3
Returning
{:reply, reply, new_state, timeout}is similar to{:reply, reply, new_state}excepthandle_info(:timeout, new_state)will be called aftertimeoutmilliseconds if no messages are received.
handle_cast/2
Returning
{:noreply, new_state, timeout}is similar to{:noreply, new_state}excepthandle_info(:timeout, new_state)will be called aftertimeoutmilliseconds if no messages are received.
handle_info/2
Return values are the same as
handle_cast/2.
minhajuddin
The problem with those timeouts (in my use case) is that any message to the GenServer will cancel them. However, in my use case we wanted our timer to slide or timeout based on messages from a specific process.