Similar projects

[daurnimator]

Not sure if you've seen it before, but I was working on https://github.com/daurnimator/luasodium

Probably worth trying to keep our APIs the same

[morfoh]

Thanks a lot for pointing me to your sodium lua ffi bindings! I totally agree with you that keeping the same API would be good, especially considering the fact that the C API compatibility between sodium and NaCl is a big benefit for the users already! Keeping that principle is from my point of view definitely the right way to go! Just imagine how nice it would have been to have a safe drop-in replacement for openssl these days - but that is another story! ;)
Regarding the lua-sodium bindings I started I am more bothered by the fact that due to other work I need to do at the moment, I cannot really dedicate time to it. Even some days before your message I thought about in dropping the very few stuff I already did there in favor of some pure lua ffi bindings. The initial goal of using LuaNativeObjects was to provide both - ffi and "standard bindings" - within one module but there are some oddities when working with LuaNativeObjects and the development of it seems to be stalled as well.
Personally I am using luajit most of the time now not caring much about "stock lua", majorly because of the intransparent and closed development style of the project but of course also because of the difference in speed and resource consumption between the 2 interpreters.
That said - I could perfectly live with pure lua ffi bindings right now and maybe it might be worth thinking about working together on it to provide a nice Lua API for sodium. If there is a need for non-ffi bindings they can be done as well either being part of the same project or external but following the same already existing and hopefully matured API.

Cheers,
Chris

[daurnimator]

Regarding the lua-sodium bindings I started I am more bothered by the fact that due to other work I need to do at the moment, I cannot really dedicate time to it.
I'm in a similar position, but luckily libsodium doesn't change too fast :)

To keep my motivation up I really need a long term project that uses libsodium...

Even some days before your message I thought about in dropping the very few stuff I already did there in favor of some pure lua ffi bindings. The initial goal of using LuaNativeObjects was to provide both - ffi and "standard bindings" - within one module but there are some oddities when working with LuaNativeObjects and the development of it seems to be stalled as well.

Yeah.... when I first saw your bindings I hadn't seen LuaNativeObjects before... they're quite tricky.
I don't know if I could be bothered using it personally, hence why I suggested API compatability rather than merging projects.

Personally I am using luajit most of the time now not caring much about "stock lua",

Me too; though some days I decide Lua 5.2 is where I want to be.

I'm not clear on where to take things from here; do we want to agree on one low level api and then try and build common abstractions on top?