3 hours ago · Tech · hide · 0 comments

I wrote a few weeks ago about wanting to move the OCaml based software I wrote to host this and my other websites, called Webbplats, over to OCaml's new Effect based I/O system (EIO). My motivation for doing so was simply that EIO is built by a bunch of my colleagues and so I wanted to learn what they'd been up do. The main promise of EIO as a user is that it handles blocking I/O without littering your code with promises or async/await annotations, rather your code that uses it just reads like a regular blocking I/O implementation, but under the hood EIO is juggling things to make it all work nicely. Obviously if you don't tell it to do something else whilst waiting then it will just be like a blocking implementation, but if you're using an EIO library, like say a web server library that is EIO aware as I'm about to, then that library can do the scheduling bits and your request handling code can remain quite linear. The challenge, as I documented before, was that I was previously…

No comments yet. Log in to reply on the Fediverse. Comments will appear here.