Rejoice! I have somehow managed to revive my blog without having to write any code, change any CSS or do any busy work at all thanks to the miracle of Github pages and the fact that my website was always just a pile of static pages generated by some terribly written JS that hasn't changed in nearly a decade - who says code rots? Where the hell have...

Previous entries in this series: Purerl Updates - Processes and Self Purerl Updates - Subscriptions Purerl Updates - Untagged Unions Purerl Updates - Maxing out Pinto OTP Purerl Updates - GenStatem One of the big advantages of using an existing language like Purescript when building out typed support for Erlang, is the presence of existing...

Seems we've ended up with a small handful of posts about the latest Purerl updates! Great - that's about one for every reader, let's get cracking! Purerl Updates - Processes and Self Purerl Updates - Subscriptions Purerl Updates - Untagged Unions Purerl Updates - Maxing out Pinto OTP One of the big motivations for the big push on purescript-erl-pinto...

Yes, another blog post about Purerl, following on from Purerl Updates - Processes and Self Purerl Updates - Subscriptions Purerl Updates - Untagged Unions When I first threw together Pinto, it was with the aim that there simply be a usable path for building supervision trees and gen servers, and not that we would have access to the full functionality...

Yes, another blog post about Purerl, following on from Purerl Updates - Processes and Self Purerl Updates - Subscriptions We are now here to talk about untagged unions and how they can be used when dealing with legacy messages being sent to our process and why we might want to do something differently at all. Consider a dependency to a legacy...

Two blog posts in a week? Unheard of - following on from Tuesday's blockbuster smash hit epic "Purerl Updates - Processes and Self", today we have an entry describing our current thoughts on subscriptions in a Purerl world. A standard procedure in Erlang, is to invoke an API that then proceeds to send messages back to the invoking process. some_api:subscribe()...