In our shop we actually use all of Ruby, Node, Go, Python and Bash (in about that order of code volume).  Honestly, for instability of 3rd party libraries Node is pretty bad, but Ruby is not really far behind.  I am sure that I have spent more time debugging other people&#x27;s code in Ruby than in Javascript.<p>Having said that the IO split has been a royal PITA.  We got pegged to Node 10.x because JSDom only supports IO and Jest (which is what we wanted JSDom for) only supports Node :-P.  I&#x27;ve been waiting a year for it to get cleared up.<p>It sounds like we made the right choice, though, because in this thread the people who are complaining about Node seem to be the ones who tried switching back and forth between IO and Node.  There is actually only one bug in Node that has impacted me (related to the way connections are shut down) and it isn&#x27;t fixed yet in master so not upgrading hasn&#x27;t really impacted us.  We just have to live without some of the ES6 features.<p>Personally, I&#x27;m a big fan of Go (old C++ programmer).  We started using it a little over 2 years ago.  The language definition has changed in that time, so I wouldn&#x27;t call it stable ;-)  The core libraries are rock solid, though.  We barely use any 3rd party libraries (I think we use 2) so it&#x27;s not really fair to compare that with other languages.<p>Although we have a fair amount of python in our shop, I don&#x27;t seem to work on those projects very much (a month here and there).  I can&#x27;t say too much about it other than our Python code breaks due to 3rd party libraries more often than any of our other code.  However, I think this is probably due to injudicious choices for our 3rd party libraries ;-)<p>Overall, I would say that my experiences don&#x27;t match yours, but I wonder if it&#x27;s because we never tried moving to IO.