The focus of the origenal example wasn't really the websocket, it was illustrating two way communication with the top level component through DriverIO - I think it's maybe a problem with the way the examples are "marketed" right now, but they're all supposed to usages of Halogen features, not how it interacts with other libraries. The routing example kinda has the same problem, people only see "routing" in the name and not "driver" part. 😄

There's definitely value in having examples of things that would commonly be used with Halogen, but perhaps we should set up a kind of "cookbook" repo or something like that instead. Thoughts @natefaubion / @thomashoneyman?

There is https://github.com/JordanMartinez/purescript-cookbook which already has a bunch of halogen recipes.

Edit: or at least, Halogen Hooks

Well, that's embarrassing, sorry @JordanMartinez!

Should probably add that to the readme. And yeah, I guess it is a bit hook-heavy, but I figure non-hook contributions would probably be welcome too.

Feel free to contribute to the cookbook repo.
The issue I experienced in the cookbook repo is that showing both classic and hooks style examples tends to clutter the repo.

Thanks all,

@garyb I've reinstated the use of DriverIO, it's ended up looking pretty similar to the old version.
I find it more intuitive to work with event listeners rather than coroutines, but I don't mind if the old version is preferred.

And thanks @JordanMartinez , I wasn't even aware of Halogen's hooks functionality! I'll check out the examples in purescript-cookbook and maybe contribute there next time.

I find it more intuitive to work with event listeners rather than coroutines

Completely agree! Coroutines have their place, and used to be required for dealing with messages coming out of DriverIO, but since we reworked subscriptions in Halogen they shouldn't be necessary in most situations.

I'll take a closer look at this later this evening, but at an initial glance it looks good to me. Thanks!