Marak
commented
9 years ago Hi!
Related #142
The main barrier we have right now is that we don't have any direct support for using compiled languages in our services. We have no compile step or a safe place to store compiled binaries ( yet ).
If you are saying that it's possible to implement Go support without making any major modifications to our stack ( using the scripts method described above ), it could be a good first step.
If you look at how the other languages are implementing in https://github.com/bigcompany/hook.io/tree/master/bin you can get an idea for how it would be setup.
I'm a fan of adding Golang to the platform. I just don't want to commit to having to implement support for compiled languages (right now) because it will increase our complexity.
Do you think using Golang "scripts" is an acceptable first step?
A few of us idle in #hook.io on irc.freenode.net. Please feel free to join us there.
Hey all, great looking service! And I appreciate that it's Open Source. :)
What are the barriers to Golang support? Compilation is very rapid, so much so that you can even add a shebang like
#!/usr/bin/env go runand treat programs like "scripts" (though that's wasteful..). It's fairly safe, and will prevent compilation on non-typesafe code for the most part. It's very efficient and can scale to thousands of connections even when run "bare" without a fronting webserver.Google App Engine supports Go but disables the
unsafeandreflectlibraries; presumably these are useful in escaping sandboxes or causing server woes.Thoughts?