purescript-deku VS purescript-behaviors

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.

Zora was created by Justin Garcia to improve static site generation and server side rendering in purescript-deku. Before Zora, Deku relied on a Byzantine assemblage of ad hoc typeclasses to achieve SSR. This resulted in sprawling error messages and poor type inference.

My little web framework purescript-deku runs on an event-based architecture, so I'm thinking about IsEvent quite a lot these days.

Here's an application that fulfills all four criteria. It's written using PureScript Deku, a small library I created to experiment with event-based architectures in the DOM.

I should take a moment to say that, like most things in PureScript, I learned this from Phil Freeman. He has a Semantic type that works slightly differently but is based on the same general ideas.

klank.dev is a PureScript sandbox for interactive animations and audio. It uses a technique called Functional Reactive Programming, and more specifically the Behavior pattern, to turn a phone, tablet or comptuer into a musical instrument.