it seems many big web projects (rails, django, etc. GIL langs) chose go(lang) to write "services" that could be separated. Yet, just about any language with quick execution, quick startup(?), concurrency (and/or parallelism), and a garbage-collecter would work: lisps, ocaml, haxe, nim, crystal, CLI langs (now /w AOT), JVM langs! I wonder what HN folks used. Was it a good choice?
i was specifically thinking about crystal for rails, as i noticed a few interesting repos: mosquito, a job scheduler; fruit-juice, a ruby gem to enqueue jobs into mosquito (especially from rails); and lavinMQ, a successor of rabbitMQ(?).
https://github.com/mosquito-cr/mosquito | https://github.com/crimson-knight/fruit_juice | https://github.com/cloudamqp/lavinmq/
i was specifically thinking about crystal for rails, as i noticed a few interesting repos: mosquito, a job scheduler; fruit-juice, a ruby gem to enqueue jobs into mosquito (especially from rails); and lavinMQ, a successor of rabbitMQ(?).
https://github.com/mosquito-cr/mosquito | https://github.com/crimson-knight/fruit_juice | https://github.com/cloudamqp/lavinmq/