What I (personally) don't like about putting side-effects in action creators is that these functions become impure, hard to test and if there are many side effects they can get very messy. Although, for me the main reason would be that the logic is then spread across dozen of files (reducers, action creators, ...) and that's something I don't really like with redux.

With this declarative approach you have a really clear idea of what's happening in terms of both side effects and state just by looking at the reducer.

Once again, if you're happy with putting them in action creators, it's completely fine. It's a matter of taste I guess and you should probably use what you're the most comfortable with.

I took this idea from re-frame in clojurescript. When going back to JS and redux I thought I missed this approach, so I made this small thing.

Not bad I am a big fan of core.async, you definitely need to add a leaderboard though...

Didn't think of adding a leaderboard before. Will do it then :)

Thanks! Indeed there are a lot of things to fix/improve! It was only supposed to be a simple project to build something with elm, but it looks like people actually like it. I'll try to fix all these things really soon!

you can try it out, I just added a username/password login

You can re-open a tab now an try it out, I just added a username/password login

Thanks for the feedbacks, just added a login with username/password

You should be able to try it out now!

I quickly created a signup/login form, you should be able to try now