[slindz]

I have two projects on the go right now. Both have gone the web sockets first approach. I love it.

For me, the project I keep rebuilding to learn new languages/frameworks is Risk (though it's been quite awhile now).

After spending so much time with Phoenix channels on my main project, I couldn't resist the fun of reimplementing it over sockets. It'll probably wind up on GitHub when I'm done.

[Kexoth]

But isn't channels the Phoenix abstraction (middleware) for websockets/sockets per se?

What I mean is why not write a sockets Phoenix channels transports adapter to be used instead of the default one & continue using the existing codebase? :)

[slindz]

Sorry! Reading my comment back, it's no wonder it was tough to follow.

Instead of writing: "I couldn't resist the fun of reimplementing it over sockets."

I should have wrote: "I couldn't resist building another version of Risk with Phoenix/channels/sockets because it should be mind-meltingly easier compared to all of the previous times I'd built it on other platforms"

[lilactown]

I assume the OP is talking about reimplementing the channels client. Though now I'm not sure.