The thing is, you can still do all this in Apache now. CGI still exists (in fact, it's the default way Perl's ran). So I'm really struggling to work out why I'd install their tool over Apache.
And I don't mean this negatively, I really do want to know what separates this product from existing webservers runing CGI, but there's no useful information on their website what-so-ever.
If any of the Rebin devs are reading this, are you able to elaborate on this tool a little more?
Hi, one of the developers here. Not all servers run CGI. Sure, while there are wrappers that can do it, for example for nginx, it isn't pretty. The purpose for REBIN is a clear and concise serving of executables without the overhead of say Apache. I think the readme is rather verbose... Call me surprised :)
To be brutally honest, the readme didn't really sell the product. But then I guess that's not the point of the readme. However none of your other documentation (blog posts, Rebin product page, etc) explained what sets this product apart either.
I think I get it's point now - though I can't pretend to be sure of that. I can see that you're trying to do something a little different from CGI (which, incidentally is available for node.js as well), I'm just not entirely sure how different you two are. I guess the proof of that may just be in using it :)
Either way, it's good to see it up on github and I'm sure plenty people will be grateful for your work.
If this was a small tool with no dependencies, then it would be a clear winner over a heavy-weight install of apache, just to serve it. But, as is, I don't see the real benefit over apache, unless you already have redis and node running.
And I don't mean this negatively, I really do want to know what separates this product from existing webservers runing CGI, but there's no useful information on their website what-so-ever.
If any of the Rebin devs are reading this, are you able to elaborate on this tool a little more?