Software development dumping ground
Dormant Last read · last published · next check
Read 13 hours ago and current, but nothing has been published for 3 years.
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 I been? I'm honestly quite surprised at how many…
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 tooling and libraries for the language (such as language…
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 was to facillitate the addition of other OTP…
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 of those things straight out of the gate. This…
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 Erlang library that has a subscribe call that sends us…
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() receive Msg -> .. More often or…
It has been about three years since I first sat in a hotel in Lithuania throwing together the first versions of purescript-erl-pinto and purescript-erl-stetson so that we could get started on a project for one of our clients. Quite a lot of code has been written against those projects internally by colleagues and myself and over time: Various improvements/patterns have been discovered within core…
TLDR: Erlang.NET Released on Github I've been working in Erlang now for nearly a decade and for the last year or two we have been investigating what it would take to start writing a lot more of that Erlang in Purescript instead because in theory working in a sensibly typed language means fewer bugs means fewer support calls means more time spent working on features which can be sold and therefore…
Hot on the heels of my last post about integrating Dotnet with Erlang , I was asked by a friend "Hey that looks really cool, we're stuck with Elixir at work currently - is there a migration path for us? Well I'm glad you asked, Erlang.NET does indeed work with Elixir and to prove it, I've built a skeleton application over on Github. What does it look like? Well, first of all let me say that I've…
This blog entry is part of my " blog about mundane stuff " series. I covered my decoding test before having a look at context management , so now it's time to look at re-encoding the h264 and demonstrating a round trip through the nvidia hardware. What we have already We had this workflow for testing #workflow { generator = #read_from_ts { name = source, filename = << "foo.ts" >> }, processors = […
