|
SavageMessiah posted:I don't follow, how does not having dynamic linking make it hard to write a good library? Because a heck of a lot of library writing for new languages is about bindings for tried and tested existing C libs. Has someone got a SWIG thinger working for GO yet? edit:  TOOT TOOT http://www.swig.org/Doc2.0/Go.html TOOT TOOT
|
#
¿
Mar 30, 2014 21:52
|
|
|
|
| # ¿ Apr 29, 2024 01:45 |
|
|
Is it just me or do a lot of Go's libraries have utterly garbage documentation. Maybe I'm spoiled by python, but I'm coming across so many libraries that have at best a minimal API documentation and no context at all.
|
|
#
¿
Mar 12, 2015 12:48
|
|
|
good jovi posted:Running the Go process on a higher, unprivileged port and proxying is the way to do it. Look into something more powerful than nohup for running your code, though. I use daemontools at work and it's fine, but I think supervisor is a bit more reasonable to set up. You want something that will handle stdout/stderr redirection, restarting the process when it crashes, and reporting on process status. Honcho (A python heroku like thing that does Procfiles and .env files) can export out to supervisord. Its really handy for turning 12 factor type apps into non retarded systemd apps.
|
|
#
¿
Mar 16, 2015 07:23
|
|
|
First Time Caller posted:http://www.gopl.io/ Brian Kernigan co wrote it? Well thats got my attention!
|
|
#
¿
Oct 27, 2015 03:26
|
|