io-sim VS purescript-halogen

It is implemented using our own io-sim library: https://github.com/input-output-hk/io-sim - which I hope to put on Hackage in future.

There's a framework in purescript from which u can grab some ideas I think: https://github.com/purescript-halogen/purescript-halogen.

If you wanna do web frontends right now, I'd recommend Halogen for Purescript since it is maintained and has documentation.

Before 2012, all of my websites were made using HTML, CSS and a sprinkling of JS. Then, I went all-in on AngularJS, followed by React. I started using Typescript and then PureScript and learned more frameworks like Halogen and Concur. I even wrote my own UI framework called purescript-deku.

First of all I had to choose what to use to manage the User Interface. I narrowed down to two modules: Halogen and react-basic-hooks (which is a “wrapper” of the unmaintained react-basic). I decided to go with react-basic-hooks just because I work with React on a daily basis and I wanted to understand its interoperability with PureScript. I will 10/10 try Halogen too in the next future since as far as I can see is the most famous and maintained in the PureScript community.

There's also Purescript, which is sort of a Haskell for frontend. It has type classes, HKTs and so on and also has a very nice FFI. When it comes to UI libraries there is Halogen which I think is very well though out and allows for using tagless final approach. There's also react-basic but I haven't used that one myself.

Yeah? I wrote something to deal with it too (https://github.com/toastal/return-optics) 5.5 years ago. You arguably chose the wrong data as `(model, Cmd msg, Maybe extMsg)` instead of `(model, Cmd msg, List extMsg)` which would give you more flexibility and still functions as a monoid on [] instead of Nothing, but allows multiple messages shrug. I tried this approach more recently and it involved me having to encode all of actions in a massive tree and then I still had issues with certain messages including now having to UUID all elements that that previously I didn't need to think about. It was a mess, but the best I could do with the tools at hand.

If you compare this to Halogen (https://github.com/purescript-halogen/purescript-halogen/blo...) where you still have purity but can set up subscribers and listeners from any component. It's much easier to use and for some components like dialogs, it's much simpler. And this actually isn't the best example because with the latest Halogen, Portals (https://github.com/purescript-halogen/purescript-halogen/pul...) was introduced so you can launch a dialog on the spot instead of even needing to communicate between them at all.

Below you can find the example of a simple button component written in Halogen:

Hi just to answer your Purescript question. I've been using Purescript for some time now in production and I really like it. I've been using purescript-halogen which is a reactive framework, similar to React, Vuejs etc. I feel Purescript has a lot of top quality libraries and they have been increasing lately. But just like with Haskell there will be abandoned repositories and undocumented experiments and sometimes it has to do with the fact that both Haskell and Purescript have fewer maintainers than some other languages. But my experience is that a lot of the libraries that are written are well implemented and very usable.