Having used "Scripting Bridge" for a few years now, I'm keenly aware of its very real and common caveats, and I'm not comfortable using it in any serious project. If users would like to write something like Hydra using only LuaObjC[1] or something similar, they're free to. But manually bridging function calls gives Hydra a robustness and stability that such an automatic bridge can never truly have.
I'm sure you wouldn't have bothered with the project if you didn't perceive it as being a better approach. I'm just ignorant to what the advantages are. Is the bridge really unstable? I hadn't noticed that with my admittedly limited exposure.
Comments
Having used "Scripting Bridge" for a few years now, I'm keenly aware of its very real and common caveats, and I'm not comfortable using it in any serious project. If users would like to write something like Hydra using only LuaObjC[1] or something similar, they're free to. But manually bridging function calls gives Hydra a robustness and stability that such an automatic bridge can never truly have.
[1] https://github.com/darrenclark/LuaObjC
I'm sure you wouldn't have bothered with the project if you didn't perceive it as being a better approach. I'm just ignorant to what the advantages are. Is the bridge really unstable? I hadn't noticed that with my admittedly limited exposure.
I'm just weary of any bridge to ObjC, having seen the caveats first-hand. But I suppose it's mostly just in principle.