That makes sense - Iâm getting the impression that ffi is getting very easy these days and maybe we should use it more to focus on âotherâ things. It does complicate deployment a bit - but if youâre server/cloud based then thatâs less of an issue anyway . This said, many of our nastiest bugs seem to centre around ffi a c based libraries - but maybe using them more will tease this out. Tim Sent from my iPhone
On 2 Jan 2020, at 01:27, Pierce Ng <pierce@samadhiweb.com> wrote:
On Wed, Jan 01, 2020 at 02:35:03PM +0100, Tim Mackinnon wrote: Iâm curious why you chose to use ffi for this one in particular as it would seem to be quite straightforward to do it all in native Smalltalk (not to down play your integration in any way of course). Was performance a big thing? Or was it simply relying on others to keep it up to date?
I wanted something that works out of the box. I did not want to implement MD parsing myself.
Also I saw hoedown's wiki page on bindings and thought I'd put Smalltalk on the map there.
https://github.com/hoedown/hoedown/wiki/Bindings
Pierce