3 ms·

If you deployed Go in production, I'd love reading about that since I'm having a closer look at it now (coming from Ruby). Is there a more widely used option cu

If you deployed Go in production, I'd love reading about that since I'm having a closer look at it now (coming from Ruby). Is there a more widely used option currently?

jlgreco 14y ago
Looking at the source, and having looked at how nginx does it, this looks like a pretty straightforward implementation with no real frills. I imagine anyone doing this in production with Go already has just rolled their own solution not much unlike this (doing this for some pet projects of mine has been on my TODO for a few weeks, never got around to it though).
dsl 14y ago
Unless you are a committer to Ruby now, or plan to invest in learning more powerful languages, Go probably isn't a good choice. I run a pure Go shop and we generally look for people with hardcore C (not C++ or C#) or systems/kernel backgrounds or at least one open source Go library under their belt. If you're just looking for another language to get away from the cesspit that is Ruby, try Python.
- cmccabe 14y ago
  Hey man... hire people, not years of experience in X. Let's not pidgeonhole people because of what languages they've used in the past.
- thibaut_barrere 14y ago
  Do you mean you believe that people using Ruby are either Ruby committers, or people with only pure Ruby experience? If this is true, I think you'll miss some great candidates, to be honest. Things I did before, for instance, include: - writing real-time 2D/3D rendering engines, mixing C++, TurboPascal, Asm - low-level assembly code, writing keyboard hardware interrupt handlers, TSR, video-cards tweaking etc - porting C-libraries from Solaris to Windows - writing a full GUI toolkit - writing 2D games - wrapping C and C++ libraries into .Net - writing a cluster of satellite images processing with PVM Etc (apart from using Java, .Net, Ruby, CoffeeScript etc). To make my point clear: the good rubyists I know have a lot of past experience, similar to this. Talking about "cesspit" is not giving good signals about how you consider other technical choices, either :-)

If you deployed Go in production, I'd love reading about that since I'm having a closer look at it now (coming from Ruby). Is there a more widely used option currently?

jlgreco 14y ago

Looking at the source, and having looked at how nginx does it, this looks like a pretty straightforward implementation with no real frills. I imagine anyone doing this in production with Go already has just rolled their own solution not much unlike this (doing this for some pet projects of mine has been on my TODO for a few weeks, never got around to it though).

dsl 14y ago

Unless you are a committer to Ruby now, or plan to invest in learning more powerful languages, Go probably isn't a good choice. I run a pure Go shop and we generally look for people with hardcore C (not C++ or C#) or systems/kernel backgrounds or at least one open source Go library under their belt. If you're just looking for another language to get away from the cesspit that is Ruby, try Python.

cmccabe 14y ago
Hey man... hire people, not years of experience in X. Let's not pidgeonhole people because of what languages they've used in the past.
thibaut_barrere 14y ago
Do you mean you believe that people using Ruby are either Ruby committers, or people with only pure Ruby experience? If this is true, I think you'll miss some great candidates, to be honest. Things I did before, for instance, include: - writing real-time 2D/3D rendering engines, mixing C++, TurboPascal, Asm - low-level assembly code, writing keyboard hardware interrupt handlers, TSR, video-cards tweaking etc - porting C-libraries from Solaris to Windows - writing a full GUI toolkit - writing 2D games - wrapping C and C++ libraries into .Net - writing a cluster of satellite images processing with PVM Etc (apart from using Java, .Net, Ruby, CoffeeScript etc). To make my point clear: the good rubyists I know have a lot of past experience, similar to this. Talking about "cesspit" is not giving good signals about how you consider other technical choices, either :-)